Favicon of root-instructions

root-instructions Skill

AI Agent SkillTypeScriptOpen source

Generate a concise .github/copilot-instructions.md file for a repository by analyzing its codebase structure, tech stack, and conventions. Published by microsoft in agentrc.

Decision snapshot

Is this a fit?

Best for

Testing, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

2 months ago · MIT license

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is root-instructions Skill?

Generate a concise .github/copilot-instructions.md file for a repository by analyzing its codebase structure, tech stack, and conventions. Published by microsoft in agentrc. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
74/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Testing
  • Testing use cases

Declared skill metadata

  • Source file: plugin/skills/root-instructions/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use root-instructions Skill

  • Use it for testing.

Built with

TypeScriptCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/agentrc
  • Skill file: plugin/skills/root-instructions/SKILL.md

What it does

Generate a concise .github/copilot-instructions.md file for a repository by analyzing its codebase structure, tech stack, and conventions.

Skill instructions

You are an expert codebase analyst generating a .github/copilot-instructions.md file. Exploration Strategy Fan out multiple Explore subagents to map out the codebase in parallel: 1. Check for existing instruction files: glob for /{.github/copilot-instructions.md,AGENTS.md,AGENT.md,CLAUDE.md,.cursorrules,README.md,.github/instructions/.instructions.md} 2. Identify the tech stack: look at package.json, tsconfig.json, pyproject.toml, Cargo.toml, go.mod, .csproj, .fsproj, .sln, global.json, build.gradle, pom.xml, etc. 3. Understand the structure: list key directories 4. Detect monorepo structures: check for workspace configs (npm/pnpm/yarn workspaces, Cargo.toml [workspace], go.work, .sln solution files, settings.gradle include directives, pom.xml modules) Output Guidelines Generate concise instructions (~20-50 lines) covering: - Tech stack and architecture - Build/test commands - Project-specific conventions - Key files/directories - Monorepo structure and per-app layout (if this is a mon

Verified compatibility and discovery

Frequently asked questions

What is root-instructions?

root-instructions is a open-source AI agent skill with Copy skill directory. Generate a concise .github/copilot-instructions.md file for a repository by analyzing its codebase structure, tech stack, and conventions.

Who is root-instructions best for?

root-instructions is best for reusing agent instructions, scripts, and references, testing workflows.

How do I install root-instructions?

Install or run root-instructions using Copy skill directory. Check root-instructions for the latest setup command.

Is root-instructions actively maintained?

root-instructions may need a closer maintenance check before production use.

Share:

Stars
957
Forks
86
Last commit
2 months ago
Last verified
Aug 28, 2026
Metadata fetched
Aug 28, 2026
Repository age
7 months
License
MIT

Project health auto-fetched from the source repository.

Maintain this resource?

Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.

Alternatives to root-instructions