Apply an approved BOOT upgrade item by number using the guided apply runner.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add NeverSight/skills_feed --skill gov_apply --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Gov Apply?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/neversight-gov-apply)More formats (shields.io, HTML) on the badges page.
---
name: gov_apply
description: Apply an approved BOOT upgrade item by number using the guided apply runner.
user-invocable: true
metadata: {"openclaw":{"emoji":"🧩"}}
---
# /gov_apply <NN>
## Input
- `<NN>` must be a two-digit item number, for example `01`.
## Purpose
Execute:
- `prompts/governance/APPLY_UPGRADE_FROM_BOOT.md`
- deterministic runner: `node {plugin_root}/tools/gov_apply_sync.mjs <NN>`
## Hard contract
1. If `<NN>` is missing or invalid, stop and request a two-digit number.
2. If BOOT menu context is missing, stop and request the latest BOOT menu section.
3. Apply only the approved item with deterministic runner (`tools/gov_apply_sync.mjs`).
4. After apply, run migration/audit flow as required by the apply runner.
5. For OpenClaw system claims during apply, verify against local skill docs and `https://docs.openclaw.ai`.
- For latest/version-sensitive claims, also verify official releases `https://github.com/openclaw/openclaw/releases`.
- If verification cannot be completed, report uncertainty and required next check; do not infer.
6. For date/time-sensitive claims during apply, verify runtime current time context first (session status).
7. Use runtime `<workspace-root>` semantics; do not assume fixed home paths.
8. Brain Docs routing:
- If apply path touches Brain Docs (`USER.md`, `IDENTITY.md`, `TOOLS.md`, `SOUL.md`, `MEMORY.md`, `HEARTBEAT.md`, `memory/*.md`), enforce Mode C and require explicit READ evidence before any write.
## Output requirements
- Include `FILES_READ` (exact paths) and `TARGET_FILES_TO_CHANGE` (exact paths).
- If either field is missing, output `BLOCKED (missing read/change evidence)` and stop.
- Use this output order for UX consistency:
1. `STATUS`
2. `WHY`
3. `NEXT STEP (Operator)`
4. `COMMAND TO COPY`
- Always include a final `NEXT STEP (Operator)` section.
- After apply completes:
- primary: `/gov_migrate` then `/gov_audit`
- fallback: `/skill gov_migrate` then `/skill gov_audit`
- If apply is BLOCKED:
- output one clear unblock action and the exact command to retry.
## Fallback
- If slash command is unavailable or name-collided, use:
- `/skill gov_apply <NN>`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!