rev-harness-lifecycle
Skill0 starsChanged 3 months agoApache-2.0View on GitHub
rev_harness lifecycle: install/verify/repair/status/upgrade/uninstall; triggers: revharness入れて, doctor, repair, status, upgrade inspect. NOT: tmp掃除, packaging, session開始.
In this repository78 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/go-skills-knowledge-pack/AGENTS.mdAGENTS.md
- .agents/skills/rust-skills-knowledge-pack/AGENTS.mdAGENTS.md
- .agents/skills/typescript-skills-knowledge-pack/AGENTS.mdAGENTS.md
- .claude/skills/go-skills-knowledge-pack/AGENTS.mdAGENTS.md
- .claude/skills/rust-skills-knowledge-pack/AGENTS.mdAGENTS.md
- .claude/skills/typescript-skills-knowledge-pack/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/00-general.mdcCursor rule
- .cursor/rules/revharness-critical.mdcCursor rule
- .cursor/rules/revharness-detailed.mdcCursor rule
- auto-orchestratorSkill
- baseline-protectionSkill
- client-distribution-readinessSkill
- cloudflare-deploy-guardSkill
- codex-app-server-guardSkill
- codex-app-server-product-integrationSkill
- codex-callerSkill
- context-compactorSkill
- cursor-callerSkill
- delegated-development-disciplineSkill
- deploy-command-disciplineSkill
- design-principlesSkill
- development-constitutionSkill
- development-junk-cleanupSkill
- go-skills-knowledge-packSkill
- harness-official-docs-updateSkill
- naming-normalization-guardSkill
- orchestrator-bootstrapSkill
- payload-cms-deploy-guardSkill
- production-function-implementerSkill
- research-handoffSkill
- review-workflowSkill
- root-cause-first-disciplineSkill
- rust-skills-knowledge-packSkill
- scope-guardSkill
- self-growth-proposal-triageSkill
- shared-client-wrapper-safetySkill
- slice-designerSkill
- staff-code-reviewerSkill
- structured-mentorSkill
- supabase-deploy-guardSkill
- system-plannerSkill
- typescript-skills-knowledge-packSkill
- auto-orchestratorSkill
- baseline-protectionSkill
- client-distribution-readinessSkill
- cloudflare-deploy-guardSkill
- codex-app-server-guardSkill
- codex-app-server-product-integrationSkill
- codex-callerSkill
- context-compactorSkill
- cursor-callerSkill
- delegated-development-disciplineSkill
- deploy-command-disciplineSkill
- design-principlesSkill
- development-constitutionSkill
- development-junk-cleanupSkill
- go-skills-knowledge-packSkill
- harness-official-docs-updateSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Verify: run the health check when the operator asks whether it works.
- Very specific: line 30
Do NOT use this skill for .claude/tmp cleanup.
- Very specific: line 31
Do NOT use this skill for client packaging or distribution readiness.
- Very specific: line 32
Do NOT use this skill for session start or orchestrator wake-up.
- Very specific: line 40
Use the facade subcommands exactly: install, verify, repair, status, upgrade inspect, or uninstall.
- Distinctive: line 41
Keep destructive paths dry-run/checklist first unless the user gives a separate explicit apply instruction.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Rev Harness Lifecycle
When to use
- Install: set up RevHarness in a project with the canonical facade.
- Verify: run the health check when the operator asks whether it works.
- Repair: run the repair path after a broken or partial install.
- Status: inspect current adoption phase and doctor state.
- Upgrade inspect: review upgrade state without applying mutation.
- Uninstall checklist: print the removal checklist; require explicit user intent for destructive apply.
Trigger phrases
| User phrase | Command |
revharness 入れて, 初回セットアップ, enable rev_harness | rev-harness install |
doctor 回して, 動いてる?, verify rev_harness | rev-harness verify |
壊れた、直して, repair rev_harness | rev-harness repair |
状態, status | rev-harness status |
アップグレード見て, upgrade inspect | rev-harness upgrade inspect |
アンインストール手順, uninstall checklist | rev-harness uninstall |
What NOT to do
- Do NOT use this skill for
.claude/tmpcleanup; usedevelopment-junk-cleanup. - Do NOT use this skill for client packaging or distribution readiness; use
client-distribution-readiness. - Do NOT use this skill for session start or orchestrator wake-up; use
orchestrator-bootstrap.
Invocation
bash scripts/rev-harness <subcommand> [options]Use the facade subcommands exactly: install, verify, repair, status, upgrade inspect, or uninstall.
Keep destructive paths dry-run/checklist first unless the user gives a separate explicit apply instruction.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

