create-instructions
Create an instructions file (.instructions.md) for a project rule or convention.
- License 许可
- MIT
- 所属仓库
- microsoft/vscode
- 最近更新
- 2026-11-12
- Stars
- ★ 20w
- Forks
- 4.4w
01 前言 Front Matter
- name
- create-instructions
- description
- Create an instructions file (.instructions.md) for a project rule or convention.
- argument-hint
- What rule or convention to enforce?
- disable-model-invocation
- true
03 SKILL.md 正文
Related skill: agent-customization. Load and follow instructions.md for template and principles.
Guide the user to create an instructions file.
Extract from Conversation
First, review the conversation history. If the user has been correcting the agent's output or asking for specific patterns (e.g., "always use X", "never do Y", "follow this style"), generalize that into a persistent instruction. Extract:
- Corrections or preferences mentioned during the conversation
- Coding patterns the user enforced or requested
- Project-specific conventions referenced
Clarify if Needed
If no clear rule emerges from the conversation, clarify:
- Should this apply everywhere or only to specific files?
- Which technologies or file types are affected?
- Is this a hard rule or a preference?
Explore the codebase using subagents if you need more context.
Iterate
- Draft the instruction and save it.
- Identify the most ambiguous or weak parts and ask about those.
- Once finalized, summarize what the instruction enforces, suggest example prompts to see it in action, and propose related customizations to create next.
Remember to follow the agent-customization guidelines to create highly effective instructions.
04 同仓库更多 Skills
sweeper-query
Answer natural-language questions about the VS Code Sweeper's published issue index (index-<name>.json for microsoft/vscode and the enrolled family repos) — which issues are agent-ready to implement or plan, what the sweeper proposed for an assignee or area, whether the sweeper knows a report as a duplicate, the highest-value open bugs in a lane — and, for one issue, the review's full record (evidence with file citations, fix brief, proposed comment). Use ONLY when the request explicitly names the sweeper — "sweeper", "vscodesweeper", "sweeper-query", a sweeper verdict, record, brief or index, an agent-ready issue — or asks what "the sweeper" found, proposed or knows. Do NOT use for general questions about issues, duplicates, priorities or ranking that do not mention the sweeper. Read-only; discovery only.
update-skills
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
sync
Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.
sync-upstream
Update a stale session branch by rebasing onto the latest origin. Use when the upstream has moved significantly and the session needs to catch up, resolving conflicts by preserving upstream changes and adapting session work to fit.
merge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.