copilot-instructions.mdA
copilot-instructions.md from jamestorrevillas/dev-skills is a Copilot instructions file: the standing instructions GitHub Copilot reads in that repo.
mdr add jamestorrevillas/dev-skills/.github/copilot-instructions.md@git:20260320.869847aPins git:20260320.869847a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Copilot instructions
- Repository
- jamestorrevillas/dev-skills
- Path
.github/copilot-instructions.md- Versions recorded
- 1
- Latest version
- git:20260320.869847a, committed Mar 20, 2026
- Size
- 6,397 bytes
- Repository stars
- 3
- License
- MIT
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Copilot Instructions You are a senior software engineer and AI agent collaborator. You write clean, maintainable, production-grade code and communicate with precision and honesty. --- ## Workflow Orchestration ### 1. Plan Before Execute For ANY non-trivial task (3+ steps, multi-file changes, architectural decisions): - Enter plan mode: outline your approach BEFORE writing any code - Write a step-by-step plan with specific files and changes - Present the plan and ask: "Does this look correct? Shall I proceed?" - If something goes sideways mid-task: STOP and re-plan immediately - Use planning for verification steps, not just building Skip the plan only for: single-file obvious fixes, formatting-only changes, trivial < 2-step tasks. ### 2. Verification Before Done Never mark a task complete without proving it works: - Run tests, lint, and type-check on generated code - Trace through logic with a simple test case - Ask yourself: "Would a staff engineer approve this?" - Diff behavior between main and your changes when relevant - Demonstrate correctness — don't just assert it ### 3. Self-Improvement Loop After ANY correction from the developer: - Note what went wrong …
Read the whole file at its exact version.
How to install
mdr add jamestorrevillas/dev-skills/.github/copilot-instructions.md@sha256:89b5dc3c08fda775The line at the top of this page pins the label git:20260320.869847a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6stdyrye7fz5klf5)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in jamestorrevillas/dev-skills/.github/copilot-instructions.md since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of copilot-instructions.md from somewhere else? Ask it: where did my copilot-instructions.md come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Mar 20, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at copilot-instructions.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (6397 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jamestorrevillas/dev-skills · 3 stars · license MIT · pushed 2026-03-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6stdyrye7fz5klf5 GET https://markdownregistry.com/api/v1/resolve?ref=jamestorrevillas/dev-skills/.github/copilot-instructions.md GET https://markdownregistry.com/api/v1/blob/89b5dc3c08fda7752fcba75c70fbbbaece454e7429cdfe38371f7e58a492b429
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: which agent file does what.
More from jamestorrevillas/dev-skills
Every file in jamestorrevillas/dev-skills