copilot-instructions.md Generator From Your Repo's Real Build, Test and Style Setup
Has GitHub Copilot inspect your repo and write a .github/copilot-instructions.md with the real build, test and lint commands and checkable conventions, plus up to three path-scoped .instructions.md files.
You getThe copilot-instructions.md content in one code block, each proposed .instructions.md file in its own code block and table
Prompt
Installs to .agents/skills/copilot-instructions-md-generator-from-your-repo-s-real-build-te/
mkdir -p .agents/skills/copilot-instructions-md-generator-from-your-repo-s-real-build-te && curl -sL "https://prompts-gpt.com/prompts/copilot-instructions-md-generator-from-your-repo-s-real-build-test-and-style-setup/raw" -o .agents/skills/copilot-instructions-md-generator-from-your-repo-s-real-build-te/SKILL.mdYou are GitHub Copilot in agent mode, working in this repository. Write a .github/copilot-instructions.md file that tells Copilot how to work here, based only on what you find in the repo.
Steps:
1. Inspect package manifests and lockfiles, Makefile or task scripts, .github/workflows, lint and format configs, test folders, the README and any existing AGENTS.md, CLAUDE.md or .github/instructions files.
2. Find the exact commands to install, build, run one test, run all tests, lint and typecheck. Take them from scripts and CI; do not guess. Run the quick, safe ones and note the result.
3. Record the folder layout, naming and error-handling conventions visible in the code, and the do-not rules: generated files, migrations, secrets, vendored code.
Rules: under about two pages; every line checkable; nothing a linter or CI already enforces; no README text copied over.
Then propose at most three path-specific files at .github/instructions/NAME.instructions.md, each with an applyTo glob in its front matter (for example src/api/**/*.ts) and only the rules that differ for that area.
Output format:
1. The copilot-instructions.md content in one code block
2. Each proposed .instructions.md file in its own code block
3. Table: command | source (script or CI file) | ran successfully
4. What you could not verifyExample output
Run in GitHub Copilot agent mode (VS Code, Visual Studio or JetBrains) at the repo root, review the commands table, then commit. Copilot coding agent and code review read these files.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Codex Writes an AGENTS.md for This Repository From the Real Setup
Has Codex inspect your repository and write a short, accurate AGENTS.md with the real build, test and lint commands, conventions and boundaries, checked by actually running them.