Skip to content

Repo Architect — Commands

FieldValue
TypeAgent Reference
Source~/.copilot/agents/_refs/repo-architect/commands.md
DescriptionNot specified

Source Content

Repo Architect — Commands

Reference for the slash-style commands the Repo Architect agent supports. The agent body links here; do not duplicate inline.

/bootstrap — full project scaffolding

  1. Detect environment

    • Check for .github/, .opencode/, AGENTS.md
    • Identify project language/framework
    • Decide: VS Code, OpenCode CLI, or hybrid
  2. Create directory structure

    .github/
    copilot-instructions.md
    agents/
    instructions/
    prompts/
    skills/
    .opencode/ # if OpenCode CLI is in scope
    opencode.json
    agents/
    skills/ -> ../.github/skills # symlink preferred
    AGENTS.md # symlink to .github/copilot-instructions.md (or distilled)
  3. Generate foundation files

    • copilot-instructions.md with project context
    • AGENTS.md (symlink or custom distilled version)
    • Starter opencode.json if CLI is used
  4. Add starter templates

    • One sample agent for the primary stack
    • One basic instructions file for code style
    • Common prompts (test-gen, doc-gen, explain)
  5. Suggest community resources — only if awesome-copilot MCP tools are present.

/validate — structure validation

Focus on structure, not deep file inspection.

  1. Required files & directories

    • .github/copilot-instructions.md exists, non-empty
    • AGENTS.md exists if OpenCode CLI is in use
    • .github/agents/, .github/prompts/, .github/instructions/, .github/skills/ exist
  2. Spot-check naming

    • lowercase-with-hyphens
    • correct extensions (.agent.md, .prompt.md, .instructions.md)
  3. Symlinks (hybrid setups)

    • valid, pointing to existing files
  4. Report — emit a status block:

    Status: Valid | Warnings | Issues
    Foundation Layer:
    OK copilot-instructions.md (1245 chars)
    OK AGENTS.md (symlink -> .github/copilot-instructions.md)
    Agents Layer:
    OK .github/agents/reviewer.md
    WARN .github/agents/architect.md - missing 'model' field
    Skills Layer:
    OK .github/skills/git-workflow.md
    ERR .github/prompts/test-gen.prompt.md - missing 'description'

/migrate — migration from existing setup

Supported sources:

  • .cursor/ rules → .github/
  • .aider/ config → .github/ + .opencode/
  • Standalone AGENTS.md → full three-layer structure
  • .vscode/ settings → distilled into Copilot instructions

Always non-destructive: copy + diff first, never overwrite without confirmation.

/sync — synchronize VS Code and OpenCode

  • Refresh symlinks
  • Propagate updates from shared skills/ directory
  • Verify cross-environment consistency (foundation files in sync, no orphan files)

/suggest — community resource recommendations

Requires the awesome-copilot MCP server. If mcp_awesome-copil_* tools are not detected, the agent skips this entirely and informs the user once.

Workflow when available:

  1. Detect MCP tools
  2. Use mcp_awesome-copil_search_instructions with stack keywords
  3. Use mcp_awesome-copil_list_collections to find curated collections
  4. Recommend, e.g.:
    • typescript-mcp-development for TS projects
    • python-mcp-development for Python projects
    • csharp-dotnet-development for .NET projects
    • testing-automation for test-heavy projects
  5. Use mcp_awesome-copil_load_collection to fetch details, then provide install links for VS Code / VS Code Insiders, or offer direct download.

Scaffolding templates

copilot-instructions.md

# Project: {PROJECT_NAME}
## Overview
{Brief project description}
## Tech Stack
- Language: {LANGUAGE}
- Framework: {FRAMEWORK}
- Package Manager: {PACKAGE_MANAGER}
## Code Standards
- Follow {STYLE_GUIDE}
- Format with {FORMATTER}
- Lint with {LINTER}
## Architecture
{High-level architecture notes}
## Development Workflow
1. {Step}
2. {Step}
## Important Patterns
- {Pattern}
## Do Not
- {Anti-pattern}

Agent (.agent.md)

---
description: '{DESCRIPTION}'
model: GPT-4.1
tools: [{RELEVANT_TOOLS}]
---
# {AGENT_NAME}
## Role
## Capabilities
## Guidelines

Instructions (.instructions.md)

---
description: '{DESCRIPTION}'
applyTo: '{FILE_PATTERNS}'
---
# {LANGUAGE/DOMAIN} Instructions

Prompt (.prompt.md)

---
agent: 'agent'
description: '{DESCRIPTION}'
---
{PROMPT_CONTENT}

Skill (SKILL.md)

---
name: '{skill-name}'
description: '{DESCRIPTION - 10 to 1024 chars}'
---
# {Skill Name}
## Purpose
## Instructions
## Assets

Frontmatter requirements (reference)

File typeRequiredRecommended
.agent.mddescriptionmodel, tools, name
.prompt.mdagent, descriptionmodel, tools, name
.instructions.mddescription, applyTo
SKILL.mdname, description

Notes:

  • agent accepts 'agent', 'ask', or 'Plan'.
  • applyTo uses glob patterns: '**/*.ts' or '**/*.ts, **/*.tsx'.
  • SKILL.md name must match the folder name (lowercase-hyphens).

Naming & size guidelines

  • All files: lowercase with hyphens (my-agent.agent.md); no spaces.
  • Skill folders: match the name field in SKILL.md.
  • copilot-instructions.md: 500–3000 chars (keep focused).
  • AGENTS.md: may be larger (CLI context window is cheaper).
  • Individual agents: 500–2000 chars.
  • Skills: up to 5000 chars plus assets.

Language presets

  • JavaScript/TypeScript — Biome (or ESLint+Prettier), Vitest, component generator
  • Python — Ruff/Black, pytest, type-hint conventions
  • Go — gofmt, table-driven tests, error wrapping
  • Rust — Cargo, Clippy, ownership patterns
  • .NET/C# — dotnet conventions, xUnit, async/await guidance