orc-handoff

Maps and safely edits non-engineer-owned files with graded checks and undo commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Non-engineers such as product managers often need to change small things like screen text, settings, or feature flags, but cannot tell which files are safe to touch or how to undo a mistake. This Skill identifies which files a non-developer can own, grades each by whether an automatic check exists, and performs single-value edits with the undo command shown before any change. ## Core Features & Use Cases - MAP mode: Scans the project for files a non-engineer can own (translations, content, validated settings, feature flags, docs) and grades each green, amber, or red based on whether a check catches mistakes, writing the result to orc-handoff/surfaces.md. - DO mode: Changes exactly one existing value through orc handoff set, showing the file, current value, check command, and undo command in a single confirmation message before editing. - Safety guarantees: Never edits red-graded files, never stages or commits, never creates new keys, and never reports an amber (manually checked) change as verified. - Use Case: A PM wants to change the empty-cart message. The Skill finds web/locales/en.json, shows the current value, the npm run i18n:check command, and the git checkout undo command, then edits, runs the check, and logs the change. ## Quick Start Ask the assistant to use the orc-handoff skill to change the empty cart text to "Nothing in here yet" and show the undo command first.

Frequently Asked Questions about orc-handoff

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

FAQPage Schema
How do I let a non-developer change website text safely?▼

Use MAP mode to find files a non-engineer can own, such as locale JSON or content markdown, and grade each by whether a check catches mistakes. Then DO mode edits one value at a time, showing the file, check command, and undo command before any change.

How does the green, amber, and red file grading work?▼

Grades come from whether a check exists, not the file type. Green means a command like npm run i18n:check catches mistakes, amber means only a manual human check exists, and red means the file drives behavior rather than displaying text and is never edited.

Can this skill edit configuration or code files?▼

It only changes values that already exist in green or amber graded files, never creates new keys, and never touches red files such as code that controls behavior. Red files are explained with a reason and a referral to the right engineer.

Does orc-handoff commit changes to git automatically?▼

No. It never stages and never commits. It prints the exact git undo command before editing, and the handoff log file it writes is never staged either, leaving all version control decisions to the user.

What happens if a check fails after an edit?▼

The skill reports what failed in plain words and shows the undo command again, but does not attempt to fix it, since fixing a failed check is considered code work. For amber files, it clearly states the change is unverified and lists the manual check a person must do.