[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CD1NK542FNNVFB5QD1SPQ7":3,"skill-same:01M6CD1NK542FNNVFB5QD1SPQ7":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M6CD1NK542FNNVFB5QD1SPQ7","pipeline-validator",null,"Validate CI\u002FCD pipelines after PR creation. Discovers pipelines, triggers runs, monitors status, diagnoses failures, applies auto-fixes, and retries. Use after any change-making skill creates a PR that needs pipeline validation.","loriensleafs\u002Fbrain","loriensleafs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F315385?v=4","01M6CCYZETMCJPTHNS258YRCBC","Peter Kloss","01M6CCYZK25T8516A39S9PCJT7",0,"MIT","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpipeline-validator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"pipeline","pipeline validator","change","validate","status","pr","validation","qa","ci","implementer","use","devops","auto","pipelines","2026-11-10 10:12:30",false,"---\nname: pipeline-validator\ndescription: Validate CI\u002FCD pipelines after PR creation. Discovers pipelines, triggers runs, monitors status, diagnoses failures, applies auto-fixes, and retries. Use after any change-making skill creates a PR that needs pipeline validation.\nlicense: MIT\nagents: [devops, implementer, qa]\nmodel: claude-sonnet-4-5\nmetadata:\n  version: 1.0.0\n---\n\n# Pipeline Validator\n\nPost-PR pipeline validation workflow. Discovers pipelines, triggers runs, monitors completion, diagnoses failures, applies fixes, and retries until all pipelines pass.\n\n## Triggers\n\n| Trigger Phrase | Operation |\n|----------------|-----------|\n| `validate pipelines` | Full 8-step workflow |\n| `discover pipelines` | Step 1: Find pipeline definitions |\n| `trigger pipeline runs` | Step 3: Queue pipeline runs |\n| `monitor pipeline status` | Step 4: Poll for completion |\n| `diagnose pipeline failure` | Step 5: Analyze failure logs |\n\n## When to Use\n\nUse this skill when:\n\n- A PR has been created and needs pipeline validation before merge\n- Pipeline runs have failed and need diagnosis\n- Auto-fix and retry cycles are needed for transient or known failures\n- Any change-making skill (e.g., `windows-image-updater`) needs post-PR validation\n\n## Process\n\n### Step 1: Discover Pipelines\n\n1. Scan the repository for pipeline definition files:\n   - `.azure-pipelines\u002F*.yml`\n   - `.pipelines\u002F*.yml`\n   - `build\u002F**\u002F*.yml`\n   - Root-level `azure-pipelines.yml`\n2. Classify each pipeline by type: PR Build, Buddy Build, Buddy Release, Other\n3. Record pipeline names and file paths\n\n### Step 2: Identify Target Pipelines\n\n1. Filter to pipelines triggered by PR events or manual dispatch\n2. Exclude pipelines that are disabled or have path filters excluding the changed files\n3. Produce a target list with pipeline name, type, and definition path\n\n### Step 3: Trigger Pipeline Runs\n\n1. For each target pipeline, trigger a run against the PR branch\n2. Use Azure DevOps REST API or `az pipelines run` CLI\n3. Record the run ID and URL for each triggered pipeline\n4. Update the PR description with pipeline run links\n\n### Step 4: Monitor Pipeline Status\n\n1. Poll each pipeline run at 60-second intervals\n2. Track status transitions: Queued, Running, Completed\n3. Set a timeout of 120 minutes per pipeline run\n4. Report intermediate status updates as PR comments (at 5-minute intervals)\n\n### Step 5: Diagnose Failures\n\nFor each failed pipeline run:\n\n1. Download the run logs\n2. Match log content against known error patterns (see [error-patterns.md](references\u002Ferror-patterns.md))\n3. Classify the failure:\n   - **Auto-fixable**: Known pattern with a documented fix\n   - **Transient**: Infrastructure flake, retry without changes\n   - **Investigation required**: Unknown pattern, escalate to human\n\n### Step 6: Apply Auto-Fixes\n\nFor auto-fixable failures:\n\n1. Apply the documented fix from the error pattern catalog\n2. Commit the fix to the PR branch with a descriptive message\n3. Push the commit\n\n### Step 7: Retry\n\n1. Re-trigger failed pipelines after fixes are applied\n2. Track retry count per pipeline (maximum 3 retries)\n3. If a pipeline fails after 3 retries, mark it as requiring investigation\n\n### Step 8: Report Results\n\nUpdate the PR description with a summary table:\n\n```markdown\n## Pipeline Validation Results\n\n| Pipeline | Type | Status | Retries | Run Link |\n|----------|------|--------|---------|----------|\n| PR Build | PR | Passed | 0 | [Run #123](url) |\n| Buddy Build | CI | Passed | 1 | [Run #124](url) |\n| Buddy Release | CD | Passed | 0 | [Run #125](url) |\n```\n\n## Constraints\n\n- Maximum 3 retry attempts per pipeline\n- 120-minute timeout per pipeline run\n- Do not auto-fix failures that modify production configuration\n- Always update the PR description with run links before monitoring\n- Log all diagnosis results, even for passing pipelines\n\n## Composability\n\nThis skill is designed to be invoked by any skill that creates a PR needing pipeline validation. The calling skill creates the PR. This skill validates it.\n\nExample integration:\n\n1. `windows-image-updater` creates a PR with image updates\n2. `pipeline-validator` is invoked with the PR number\n3. `pipeline-validator` discovers, triggers, monitors, and reports\n\nAny future migration skill (e.g., .NET version upgrades) can follow the same pattern.\n\n## See Also\n\n| Document | Content |\n|----------|---------|\n| [error-patterns.md](references\u002Ferror-patterns.md) | 12-category error diagnosis catalog |\n| `windows-image-updater` skill | Pre-PR change-making skill |\n","# Pipeline Validator\n\nPost-PR pipeline validation workflow. Discovers pipelines, triggers runs, monitors completion, diagnoses failures, applies fixes, and retries until all pipelines pass.\n\n## Triggers\n\n| Trigger Phrase | Operation |\n|----------------|-----------|\n| `validate pipelines` | Full 8-step workflow |\n| `discover pipelines` | Step 1: Find pipeline definitions |\n| `trigger pipeline runs` | Step 3: Queue pipeline runs |\n| `monitor pipeline status` | Step 4: Poll for completion |\n| `diagnose pipeline failure` | Step 5: Analyze failure logs |\n\n## When to Use\n\nUse this skill when:\n\n- A PR has been created and needs pipeline validation before merge\n- Pipeline runs have failed and need diagnosis\n- Auto-fix and retry cycles are needed for transient or known failures\n- Any change-making skill (e.g., `windows-image-updater`) needs post-PR validation\n\n## Process\n\n### Step 1: Discover Pipelines\n\n1. Scan the repository for pipeline definition files:\n   - `.azure-pipelines\u002F*.yml`\n   - `.pipelines\u002F*.yml`\n   - `build\u002F**\u002F*.yml`\n   - Root-level `azure-pipelines.yml`\n2. Classify each pipeline by type: PR Build, Buddy Build, Buddy Release, Other\n3. Record pipeline names and file paths\n\n### Step 2: Identify Target Pipelines\n\n1. Filter to pipelines triggered by PR events or manual dispatch\n2. Exclude pipelines that are disabled or have path filters excluding the changed files\n3. Produce a target list with pipeline name, type, and definition path\n\n### Step 3: Trigger Pipeline Runs\n\n1. For each target pipeline, trigger a run against the PR branch\n2. Use Azure DevOps REST API or `az pipelines run` CLI\n3. Record the run ID and URL for each triggered pipeline\n4. Update the PR description with pipeline run links\n\n### Step 4: Monitor Pipeline Status\n\n1. Poll each pipeline run at 60-second intervals\n2. Track status transitions: Queued, Running, Completed\n3. Set a timeout of 120 minutes per pipeline run\n4. Report intermediate status updates as PR comments (at 5-minute intervals)\n\n### Step 5: Diagnose Failures\n\nFor each failed pipeline run:\n\n1. Download the run logs\n2. Match log content against known error patterns (see [error-patterns.md](references\u002Ferror-patterns.md))\n3. Classify the failure:\n   - **Auto-fixable**: Known pattern with a documented fix\n   - **Transient**: Infrastructure flake, retry without changes\n   - **Investigation required**: Unknown pattern, escalate to human\n\n### Step 6: Apply Auto-Fixes\n\nFor auto-fixable failures:\n\n1. Apply the documented fix from the error pattern catalog\n2. Commit the fix to the PR branch with a descriptive message\n3. Push the commit\n\n### Step 7: Retry\n\n1. Re-trigger failed pipelines after fixes are applied\n2. Track retry count per pipeline (maximum 3 retries)\n3. If a pipeline fails after 3 retries, mark it as requiring investigation\n\n### Step 8: Report Results\n\nUpdate the PR description with a summary table:\n\n```markdown\n## Pipeline Validation Results\n\n| Pipeline | Type | Status | Retries | Run Link |\n|----------|------|--------|---------|----------|\n| PR Build | PR | Passed | 0 | [Run #123](url) |\n| Buddy Build | CI | Passed | 1 | [Run #124](url) |\n| Buddy Release | CD | Passed | 0 | [Run #125](url) |\n```\n\n## Constraints\n\n- Maximum 3 retry attempts per pipeline\n- 120-minute timeout per pipeline run\n- Do not auto-fix failures that modify production configuration\n- Always update the PR description with run links before monitoring\n- Log all diagnosis results, even for passing pipelines\n\n## Composability\n\nThis skill is designed to be invoked by any skill that creates a PR needing pipeline validation. The calling skill creates the PR. This skill validates it.\n\nExample integration:\n\n1. `windows-image-updater` creates a PR with image updates\n2. `pipeline-validator` is invoked with the PR number\n3. `pipeline-validator` discovers, triggers, monitors, and reports\n\nAny future migration skill (e.g., .NET version upgrades) can follow the same pattern.\n\n## See Also\n\n| Document | Content |\n|----------|---------|\n| [error-patterns.md](references\u002Ferror-patterns.md) | 12-category error diagnosis catalog |\n| `windows-image-updater` skill | Pre-PR change-making skill |\n",{"name":5,"model":38,"agents":39,"license":15,"metadata":40,"description":7},"claude-sonnet-4-5",[30,28,26],{"version":41},"1.0.0","main","2bd10cb7ca989f88dbf338b57957763718eda59b","templates\u002Fskills\u002Fpipeline-validator","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain","https:\u002F\u002Fgithub.com\u002Floriensleafs","2026-03-11 23:51:59",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add loriensleafs\u002Fbrain --skill pipeline-validator",{"tool":54,"command":55},"bunx","bunx skills add loriensleafs\u002Fbrain --skill pipeline-validator",{"tool":57,"command":58},"pnpm","pnpm dlx skills add loriensleafs\u002Fbrain --skill pipeline-validator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpipeline-validator\u002FSKILL.md",true,[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Ferror-patterns.md","REFERENCE","参考文档",5051,"https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fpipeline-validator\u002Freferences\u002Ferror-patterns.md",[69,82,99,122,142,163],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":33},"01M6CD3KHDHPR633RVP95G4XWN","validation-authority","Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fvalidation-authority\u002FSKILL.md",[],[76,25,77,29,28,78,79,80,81,21],"validation authority","config","behavior","tool","architect","code",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":33},"01M6CD3H29Q8FWN9YETT8YVQTS","using-brain-memory","Guidance for using Brain semantic memory effectively. Applies Zettelkasten atomic note principles with observations and relations. Use when deciding whether to query or create notes, structuring note content, or understanding the semantic knowledge graph.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fusing-forgetful-memory\u002FSKILL.md",[],[89,90,91,92,93,94,95,29,96,97,98],"using brain memory","memory","content","create","notes","graph","guidance","context","knowledge","knowledge graph",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":33},"01M6CD3E2KTTMNSWXRJAAZA7D1","threat-modeling","Structured security analysis using OWASP Four-Question Framework and STRIDE methodology. Generates threat matrices with risk ratings, mitigations, and prioritization. Use for attack surface analysis, security architecture review, or when asking what can go wrong.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fthreat-modeling\u002FSKILL.md",[],[106,107,108,29,109,80,110,111,112,113,114,115,116,117,118,119,120,121],"threat","threat modeling","prioritization","question","architecture review","stride","analysis","risk","owasp","methodology","framework","security analysis","architecture","security","go","review",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":133,"publishedAt":33},"01M6CD3BC6G0Q2MDNW6X51XHBQ","taste-lints","Custom lints with agent-readable remediation instructions. Enforces taste invariants (file size, naming conventions, structured logging, complexity) and surfaces errors that agents can act on directly. Use when writing or reviewing code to catch style violations early.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Ftaste-lints\u002FSKILL.md",[128],{"categoryNo":129,"categoryName":130,"taxonomyType":131,"taxonomyTypeDesc":132},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[134,28,135,136,29,137,138,139,140,26,81,141],"taste lints","surfaces","complexity","instructions","remediation","file","logging","writing",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":33},"01M6CD37Z7VD22BH42TG0GM66V","style-enforcement","Validate code against style rules from .editorconfig, StyleCop.json, and Directory.Build.props. Detects line ending violations, naming convention issues, indentation problems, and charset mismatches across C#, Python, TypeScript, and JavaScript. Produces JSON reports for pre-commit hooks and CI pipelines.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fstyle-enforcement\u002FSKILL.md",[],[149,150,27,32,151,152,28,153,154,155,156,157,26,158,81,22,159,160,161,162],"style enforcement","enforcement","directory","hooks","Rules","json","pre-commit","editorconfig","reports","issues","commit","javascript","python","typescript",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":33},"01M6CD35JW73TPMCZBF9DTDEE8","steering-matcher","Match file paths against steering file glob patterns to determine applicable steering guidance. Use when orchestrator needs to inject context-aware guidance based on files being modified.","https:\u002F\u002Fgithub.com\u002Floriensleafs\u002Fbrain\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fsteering-matcher\u002FSKILL.md",[],[170,29,171,172,96,173,95,139],"steering matcher","files","haiku","orchestrator"]