How do I install the Update Copilot Instructions skill?

Run npx skillmds@latest add tomevault-io/update-copilot-instructions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Update Copilot Instructions safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Update Copilot Instructions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Update Copilot Instructions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Update Copilot Instructions?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Update Copilot Instructions by tomevault-io

Name: Update Copilot Instructions
Author: tomevault-io

Update Copilot Instructions

Update Copilot instruction files to reflect current Command Center project state, architecture, phase progress, or conventions. Use when user asks to update instructions, refresh copilot context, sync instruction files with current reality, or update architecture/roadmap documentation in instruction files. Use when this capability is needed.

tomevault-io 3d1fc7b 2 files · 3.7 KB Updated Sep 17, 2026

File contents

Update Copilot Instructions — Phoenix Command Center

Repo Context

All instruction files live in:

Phoenix-Agentic-VSCode-CommandCenter/.github/instructions/

Instruction file inventory

File	Purpose
`commandcenter-architecture.instructions.md`	Module topology, message flow, supervisor integration
`commandcenter-build-and-test.instructions.md`	Build, test, lint, verify, VSIX packaging
`commandcenter-code-review.instructions.md`	Code review checklist
`commandcenter-coding-conventions.instructions.md`	TypeScript CommonJS style, VS Code patterns, webview conventions
`commandcenter-current-task.instructions.md`	Ralph Loop lifecycle, task tracking
`commandcenter-git-hygiene.instructions.md`	Branch strategy, PR flow, commit rules
`commandcenter-project-structure.instructions.md`	Directory layout reference
`commandcenter-roadmap.instructions.md`	Phase progress, milestone tracking
`commandcenter-strategy.instructions.md`	Feature placement, supervisor mode strategy

Update workflow

Read the target instruction file to understand current state
Gather current truth from source code, docs, package.json, and tsconfig.json
Apply the update using replace_string_in_file — never rewrite entire files unnecessarily
Verify the changes are consistent and accurate

Common update triggers

New source file or module added → update commandcenter-project-structure.instructions.md
Build command changed → update commandcenter-build-and-test.instructions.md
Architectural decision change → update commandcenter-architecture.instructions.md
Phase milestone completed → update commandcenter-roadmap.instructions.md
New coding pattern adopted → update commandcenter-coding-conventions.instructions.md
New webview script added → update commandcenter-project-structure.instructions.md and commandcenter-architecture.instructions.md
New command or setting added → update commandcenter-architecture.instructions.md

Rules

Only update instruction files when the actual project state has changed
Keep instruction content factual and verifiable from source
Preserve the existing format and section structure
Do not add speculative or aspirational content to instruction files
Instruction files document what is, not what will be

Source: rivie13/Phoenix-Agentic-VSCode-CommandCenter — distributed by TomeVault.

---name: update-copilot-instructionsdescription: Update Copilot instruction files to reflect current Command Center project state, architecture, phase progress, or conventions. Use when user asks to update instructions, refresh copilot context, sync instruction files with current reality, or update architecture/roadmap documentation in instruction files. Use when this capability is needed.---# Update Copilot Instructions — Phoenix Command Center## Repo ContextAll instruction files live in:```Phoenix-Agentic-VSCode-CommandCenter/.github/instructions/```## Instruction file inventory| File | Purpose ||------|---------|| `commandcenter-architecture.instructions.md` | Module topology, message flow, supervisor integration || `commandcenter-build-and-test.instructions.md` | Build, test, lint, verify, VSIX packaging || `commandcenter-code-review.instructions.md` | Code review checklist || `commandcenter-coding-conventions.instructions.md` | TypeScript CommonJS style, VS Code patterns, webview conventions || `commandcenter-current-task.instructions.md` | Ralph Loop lifecycle, task tracking || `commandcenter-git-hygiene.instructions.md` | Branch strategy, PR flow, commit rules || `commandcenter-project-structure.instructions.md` | Directory layout reference || `commandcenter-roadmap.instructions.md` | Phase progress, milestone tracking || `commandcenter-strategy.instructions.md` | Feature placement, supervisor mode strategy |## Update workflow1. **Read the target instruction file** to understand current state2. **Gather current truth** from source code, docs, `package.json`, and `tsconfig.json`3. **Apply the update** using `replace_string_in_file` — never rewrite entire files unnecessarily4. **Verify** the changes are consistent and accurate## Common update triggers- New source file or module added → update `commandcenter-project-structure.instructions.md`- Build command changed → update `commandcenter-build-and-test.instructions.md`- Architectural decision change → update `commandcenter-architecture.instructions.md`- Phase milestone completed → update `commandcenter-roadmap.instructions.md`- New coding pattern adopted → update `commandcenter-coding-conventions.instructions.md`- New webview script added → update `commandcenter-project-structure.instructions.md` and `commandcenter-architecture.instructions.md`- New command or setting added → update `commandcenter-architecture.instructions.md`## Rules- Only update instruction files when the actual project state has changed- Keep instruction content factual and verifiable from source- Preserve the existing format and section structure- Do not add speculative or aspirational content to instruction files- Instruction files document **what is**, not **what will be**---> Source: [rivie13/Phoenix-Agentic-VSCode-CommandCenter](https://github.com/rivie13/Phoenix-Agentic-VSCode-CommandCenter) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions