Create or update an instruction (.github/instructions/{name}.instructions.md) when:

• The rule should apply automatically based on file patterns (applyTo) or globally
• It's a coding convention, architectural constraint, or process rule
• It doesn't need to be invoked on demand

Procedure

1. Identify the Learning

Reflect on what went wrong or what was discovered:

• What was the problem or unexpected behavior?
• Why was it a problem? (root cause, not symptoms)
• How was it fixed or what's the correct approach?
• Can it be generalized beyond this specific instance?

2. Check for Existing Files

Before creating new files, search for existing skills and instructions that might be the right home:

# Check existing skills
ls .github/skills/ .agents/skills/ 2>/dev/null

# Check existing instructions
ls .github/instructions/ 2>/dev/null

# Search for related content
grep -r "related-keyword" .github/skills/ .github/instructions/ .agents/skills/

3a. Add to Existing File

If an appropriate file exists, add the learning to its ## Learnings section (create the section if it doesn't exist). Each learning should be 1-4 sentences.

3b. Create a New Skill

If the knowledge warrants a standalone skill:

1. Choose the location:
   • .github/skills/{name}/SKILL.md for project-level skills (committed to repo)
   • .agents/skills/{name}/SKILL.md for agent-specific skills
2. Create the directory and SKILL.md with frontmatter:

---
name: {skill-name}
description: {One-line description of when and why to use this skill.}
---

# {Skill Title}

{Body with guidelines, procedures, examples, and learnings.}

1. The name field must match the parent folder name exactly.
2. Include concrete examples — skills with examples are far more useful than abstract rules.

3c. Create a New Instruction

If the knowledge should apply automatically:

---
description: {When these instructions should be loaded}
applyTo: '{glob pattern}' # optional — auto-load when matching files are attached
---

{Content of the instruction.}

4. Quality Checks

Before saving:

• Is the learning general enough to help future sessions, not just this one?
• Is it specific enough to be actionable, not just a vague principle?
• Does it include a concrete example of right vs wrong?
• Does it avoid duplicating knowledge already captured elsewhere?
• Is the description clear enough that the agent will know when to invoke/apply it?

5. Inform the User

After creating or updating the file:

…

azure-pipelines

帮助开发者验证 Azure DevOps 流水线改动，快速排查构建与 YAML 配置问题。

skill-creator

帮助你创建、整理、校验并重构 AgentSkills 与 SKILL.md 技能文件。