orc-verify

Verifies git-modified changes with builds, tests, and severity-classified findings.

6|1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/azure-id/orc --skill orc-verify-azure-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orc-verify
Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-verify
Command: npx skills add https://github.com/azure-id/orc --skill orc-verify-azure-id

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Uncommitted code changes often ship with broken builds, failing tests, or security gaps that only surface later. This Skill runs a standalone, read-only verification pass over your working-tree changes and tells you exactly what is wrong before you commit. ## Core Features & Use Cases - Scoped Change Verification: Gathers only git-modified files via git diff, runs the build and relevant tests, and checks the diff for broken imports, removed symbols, and type errors. - Adversarial Review Pass: Attacks the diff for edge cases, error paths, contract violations, race conditions, and dead wiring, then classifies findings on a P0–P3 severity ladder with file:line evidence. - Use Case: After editing an API route and its tests, run the verify pass to confirm tests pass and catch a missing auth decorator flagged as P1 before committing. ## Quick Start Ask the assistant to verify your uncommitted changes by saying: run orc-verify on my modified files and show me the summary.

Frequently Asked Questions about orc-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify uncommitted changes before committing?▼

Run the verify pass, which collects modified files from git diff, executes the build and relevant tests, and reports findings on a P0–P3 severity ladder. It ends with a READY or NEEDS FIXES verdict and never edits or commits anything itself.

How to check only modified files instead of the whole repo?▼

The verification scope is limited to files reported by git diff, both staged and unstaged. It never sweeps the entire repository, so reviews stay focused on what you actually changed.

Does this verification tool fix or commit the issues it finds?▼

No, it is strictly read-only. It reports findings with file:line evidence and a verdict, but never edits files, stages changes, commits, or pushes. You fix issues manually or hand them to another workflow.

What severity levels does code verification report use?▼

Findings are classified P0 through P3: P0 covers failing builds, tests, and broken references; P1 covers correctness and security risks; P2 is maintainability; P3 is cosmetic. P0 and P1 block the commit verdict, while P2 and P3 are advisory.

What happens if there are no git changes to verify?▼

If the working tree has no modified or staged files, the verification stops immediately and reports that there is nothing to check. It does not fall back to reviewing the broader repository.