Menu
Delivery Gate Orchestration
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Tribunal Audit Pass that validates architecture plans against QoreLogic governance standards. Produces AUDIT_REPORT.md with PASS/FAIL verdict, unlocking the implementation gate. Use when: (1) Before /ql-implement, (2) After creating ARCHITECTURE_PLAN.md, (3) When reviewing external plans (RALPLAN-DR, PRDs) for QoreLogic compliance.
Two-phase diagnostic system combining rapid root-cause identification with residual sweep verification. Prevents cascading AI debugging damage by enforcing four mandatory analysis layers before any code change.
Implementation Pass
Session Seal
Build, refactor, and debug Bash command-line and terminal UI scripts with safe argument parsing, non-interactive fallback, and robust error handling. Use when tasks involve shell tools with flags/subcommands, interactive prompts/menus (gum/dialog/select), colored output/logging, or portable scripting on Linux/macOS.
| name | ql-repo-release |
| description | Delivery Gate Orchestration |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Edit, Write, Bash |
Orchestrate the full local release workflow after /ql-substantiate seals a session. Transitions substantiated deliverables to production-ready releases with confirmation gates at every irreversible step.
git branch --show-current
The release branch must follow the naming convention hotfix/vX.Y.Z or release/vX.Y.Z.
If on a feature branch (e.g., feat/*, plan/*):
ABORT
Report: "Cannot release from a feature branch. Create a release or hotfix branch first:
git checkout -b hotfix/vX.Y.Z (from the branch with all changes)
git checkout -b release/vX.Y.Z (from main after merging)"
If on main:
WARN: "Direct push to main is blocked by pre-push policy. Switching to release branch."
git checkout -b release/vX.Y.Z
git pull --rebase
Note: After release, create a PR to merge the release/hotfix branch into main.
Read: docs/SYSTEM_STATE.md
Read: docs/META_LEDGER.md (last entry)
Confirm the latest ledger entry is a SUBSTANTIATE seal. If not:
ABORT
Report: "No seal found. Run /ql-substantiate before releasing."
Execute release-gate.cjs --preflight from FailSafe/extension/:
node scripts/release-gate.cjs --preflight
Additionally, verify:
git diff --name-only -- .claude/commands/ql-*.md
If any skill files are modified but not committed, warn:
Skill files modified but uncommitted: [list]. Include in release commit or stash before proceeding.
Read FailSafe/extension/docs/COMPONENT_HELP.md and FailSafe/extension/docs/PROCESS_GUIDE.md. Verify version markers match the target release version. If stale, flag for update in Step 5.
Read: docs/BACKLOG.md
Verify:
[B###] references for collisionsReport any issues. If any pre-flight check fails, report which checks need attention and STOP.
Read current version from FailSafe/extension/package.json.
Ask the user:
Current version is vX.Y.Z. What bump level? (patch / minor / major)
Wait for response before proceeding.
Execute:
node scripts/release-gate.cjs --bump <level>
Report: vX.Y.Z -> vA.B.C (<level> bump)
Invoke /ql-document in RELEASE_METADATA mode with the target version:
FailSafe/extension/CHANGELOG.md — ## [A.B.C] - YYYY-MM-DDFailSafe/extension/README.md — Current Release + What's NewCHANGELOG.md — ## [A.B.C]Confirmation gate — Show authored content. User approves or edits before files are written.
INTERDICTION: Documentation versioning MUST be verified complete before any commit or tag. This gate cannot be bypassed.
Execute release-gate.cjs --preflight:
node scripts/release-gate.cjs --preflight
INTERDICTION: If ANY check shows [FAIL]:
ABORT
Report: "Documentation versioning incomplete. The following markers must be resolved:
[list each [FAIL] check with its message]
Required files for vA.B.C:
- FailSafe/extension/CHANGELOG.md → ## [A.B.C]
- CHANGELOG.md (root) → ## [A.B.C]
- FailSafe/extension/README.md → Current Release: vA.B.C
- README.md (root) → Current Release: vA.B.C + Socket badge
- FailSafe/extension/docs/COMPONENT_HELP.md → vA.B.C
- FailSafe/extension/docs/PROCESS_GUIDE.md → vA.B.C
- docs/BACKLOG.md version summary → vA.B.C row
Return to Step 5 and complete all missing documentation before proceeding."
Only when all checks show [PASS] may you proceed to Step 7.
Confirmation gate — Show the user the diff:
git diff --stat
Ask: "Stage and commit these changes as [RELEASE] vA.B.C? (y/n)"
If confirmed:
git add -f FailSafe/extension/package.json FailSafe/extension/CHANGELOG.md FailSafe/extension/README.md FailSafe/extension/docs/COMPONENT_HELP.md FailSafe/extension/docs/PROCESS_GUIDE.md CHANGELOG.md README.md docs/BACKLOG.md
git commit -m "[RELEASE] vA.B.C"
Note: -f is required because FailSafe/extension/docs/ is in .gitignore but tracked.
Execute:
node scripts/release-gate.cjs --tag
This runs preflight internally and creates an annotated git tag.
Confirmation gate — Present:
Tag vA.B.C created locally. Push to origin to trigger the release pipeline?
Remote: origin Branch: current branch Tag: vA.B.C
Proceed? (y/n)
If confirmed:
git push && git push --tags
Add META_LEDGER entry:
### Entry #[N]: DELIVER — vA.B.C
**Timestamp**: [ISO 8601]
**Phase**: DELIVER
**Author**: Governor
**Version**: A.B.C
**Tag**: vA.B.C
**Commit**: [short hash]
**Decision**: Release vA.B.C delivered. Tag pushed to trigger release pipeline.
Calculate and record content hash and chain hash per standard Merkle chain protocol.
Two irreversible actions require explicit user confirmation:
[RELEASE] vX.Y.Z without confirmed preflight PASS (the commit-msg hook enforces this at the git layer)mainmain first/ql-document for release metadata authoring[RELEASE] vX.Y.Z commit message formatdocs/COMPONENT_HELP.md and docs/PROCESS_GUIDE.mdREADME.md (root) Current Release marker and Socket badge versiondocs/BACKLOG.md version summary table: mark previous version RELEASED, add new version rowgit add -f for gitignored-but-tracked paths (e.g., FailSafe/extension/docs/)