*.instructions.md
Manage GitHub instruction files across your repositories.
Scoped `*.instructions.md` files multiply quickly and drift across repos. DirectiveOps normalizes them, detects conflicts and instruction drift, and rolls out updates with reviewable PRs.
What it is
*.instructions.md
*.instructions.md files are scoped instruction files placed in .github/instructions/. Each file provides GitHub Copilot with context for a specific area of the codebase — such as a framework, language, or domain — enabling fine-grained control over AI behavior.
The problem
*.instructions.md drift compounds silently across repos
Scoped instruction files in .github/instructions/ give teams fine-grained control over Copilot behavior per codebase area. As these files multiply across repos, keeping them consistent becomes a coordination challenge — especially when frameworks, languages, or security policies change.
How DirectiveOps helps
From drifted *.instructions.md files to aligned standards
Discover all *.instructions.md files across your GitHub org
Map scoped instructions by path, framework, and purpose
Detect conflicts and drift between scoped instruction files
Roll out scoped instruction updates via tracked PRs
Quick start
Scan for *.instructions.md locally
Run the free OSS scanner against any checkout to discover *.instructions.md files, extract directives, and review findings.
git clone https://github.com/pithpusher/DirectiveOps-Scanner.git
cd DirectiveOps-Scanner && npm install
npx directiveops-scanner scan --path .Need fleet-wide standards and rollout? See hosted plans
Related instruction files
DirectiveOps also manages these instruction files
See it in action
Walk the demo workspace
Explore the hosted dashboard with seeded data — repo inventory, drift findings, templates, and rollout controls.
Learn more
See how the product works
From discovery to tracked rollout — learn the full workflow for managing instruction files across your repository fleet.