seal
Skill14 starsChanged 49 days agoMITView on GitHub
Ships a feature; simplify, certify, commit, PR, CI, review loop, merge. Use when a feature branch is verified and ready to ship.
- Commits and pushes
In this repository24 other files it gives its agents.
- accelerateSkill
- almanacSkill
- autopsySkill
- blueprintSkill
- certifySkill
- chronicleSkill
- confluenceSkill
- conjureSkill
- deploySkill
- divineSkill
- inscribeSkill
- jiraSkill
- knowledge-graphSkill
- magicSkill
- manifestSkill
- orchestrateSkill
- portalSkill
- scrutinizeSkill
- sentinelSkill
- statuslineSkill
- transmuteSkill
- unravelSkill
- wardSkill
- weaveSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 7 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Check for the project's pre-commit skills first: .claude/skills/verify/SKILL.md and .claude/skills/simplify/SKILL.md.
- Very specific: line 35
Only
verifypresent: run the simplify pass below, and let the commit run verify in place of step 2. - Distinctive: line 36
Neither present: run the pass below and step 2 as written.
- Very specific: line 44
Run /certify. All checks must pass before you continue, style included, against the project's documented conventions …
- Distinctive: line 48
Before the commit, update the docs that describe the shipped feature:
- Distinctive: line 53
Keep the updates small and accurate.
- Very specific: line 65
When the project has a verify or simplify skill, Claude Code runs it as part of this commit.
- Distinctive: line 75
Ask "Ship this branch?" with these options:
- Distinctive: line 76
Ship it: run Push, Create PR, and Merge without a further question.
- Distinctive: line 78
Cancel: stop here. Do not push, open a PR, or merge.
- Distinctive: line 80
Treat a free-form "yes / approved / looks good" as Ship it.
- Very specific: line 89
Use the PR title and body approved at the ship-summary gate.
- Very specific: line 97
Run gh pr checks <pr> --watch with the Bash tool's background option.
- Very specific: line 112
After the merge, offer a /loop on post-merge CI with AskUserQuestion.
- Very specific: line 116
If disableGit: true: skip the push, PR and merge steps.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
/seal — Ship to Production
Take a certified feature branch through to a merged PR. This skill performs irreversible actions (push, PR, merge). It presents one consolidated ship summary and waits before the first outward command (git push).
Completion Signal
"Sealed. PR merged. Run /portal cleanup steps if applicable."
Pre-flight
- Confirm that
/certifyran and passed. - Confirm that the
/scrutinizereview and remediation cycle is complete, or that the user skipped it on purpose. - Never ship on stale evidence.
/certifymust pass in this session, with fresh output you read this turn, not a remembered run. Seelore/verification.md.
Autonomy — approve the plan, then run
Once Pre-flight is confirmed, the ship sequence runs autonomously. The simplify pass, the final certify, the documentation update and the commit proceed without a question to the owner. Claude Code's built-in read-only commands, read-only git included, do not prompt. This skill pre-approves the exact commit, push, PR, CI-check and merge commands shown below, and edits to CLAUDE.md and README.md. Any other edit or command goes through the normal permission prompt unless the user runs in auto mode.
Re-gate only on outward side effects (git push, gh pr create, gh pr merge), once, through the consolidated ship-summary gate below. Doctrine: lore/autonomy.md.
Process
1. Simplify pass
Check for the project's pre-commit skills first: .claude/skills/verify/SKILL.md and .claude/skills/simplify/SKILL.md. Since Claude Code 2.1.286, a non-bundled skill named verify or simplify that Claude may invoke runs before every commit. /almanac writes both as short delegators to /certify and to /scrutinize --lens simplifier.
- Both skills present: skip this step and step 2. The commit in step 4 runs them. Read their output when the commit returns, and fix any
Importantfinding before the ship summary. - Only
verifypresent: run the simplify pass below, and let the commit runverifyin place of step 2. - Neither present: run the pass below and step 2 as written.
The pass: dispatch magician:simplifier through Task for a final simplification sweep. Give it a self-contained prompt: the goal, the changed files with the diff, and the return format. See lore/subagent-context.md. Fix any Important finding. Skip a Suggestion unless it is trivial.
The project skills are 10-line delegators, so they do not duplicate plugin behavior. A project can replace them with its own content. Then the project skill wins. This step still runs the plugin pass when that skill does not call /scrutinize.
2. Final certify
Run /certify. All checks must pass before you continue, style included, against the project's documented conventions (lore/code-standards.md). Then a review bounce on style does not reopen the ship loop.
3. Update documentation
Before the commit, update the docs that describe the shipped feature:
CLAUDE.md: add or update changed commands, environment variables, architecture notes, or setup steps.README.md: update the feature list, screenshots, or usage examples if the change is visible to users.- Other docs that reference the changed code (API docs, architecture diagrams, and so on).
Keep the updates small and accurate. Document what changed, not the implementation details.
4. Commit
git add -A
git commit -m "feat: <feature description>
<bullet list of what was built>
Co-Authored-By: Claude <noreply@anthropic.com>"When the project has a verify or simplify skill, Claude Code runs it as part of this commit. A finding from that run goes back to step 1.
Ship-summary gate — one outward approval
Steps 1 to 4 ran autonomously. Before the first outward command (git push), present one consolidated ship summary. Then gate the outward push, PR and merge through AskUserQuestion: end your turn at the call and act on the choice. The summary covers:
- Changed files: the diff going out (from step 4's
git add -A). - Commit message: what step 4 committed.
- PR title and body: the title plus the Summary, Intent, Risk tier, How to revert and Testing from step 6.
- Merge strategy: for example
--squash --delete-branch(step 9).
Ask "Ship this branch?" with these options:
- Ship it: run Push, Create PR, and Merge without a further question.
- Revise: adjust the commit, PR, or scope first, then present the summary again.
- Cancel: stop here. Do not push, open a PR, or merge.
Treat a free-form "yes / approved / looks good" as Ship it. On Ship it, run Push (step 5), Create PR (step 6), and Merge (step 9) without a further question to the owner.
5. Push
git push -u origin HEAD6. Create PR
Use the PR title and body approved at the ship-summary gate. Do not prompt for a title again. Run gh pr create with the body from references/pr-body.md. The body carries these lines:
- Intent and Links (intent, spec and plan paths under
.workspace/shared/). - Risk tier (Low / Medium / High, from the project's
REVIEW.mdtiers when present, elselore/review.md) and the human approvals it needs. - How to revert (the exact revert command, flag or down-migration).
- Testing.
7. Watch CI (evaluator-optimizer loop)
Run gh pr checks <pr> --watch with the Bash tool's background option. On a failing check, read gh run view <id> --log-failed, fix, commit, push, and watch again until every check is green. Steps, /goal and /loop pairing, and the unattended rules (lore/unattended.md): references/ci-loop.md.
8. Review comments
If reviewers add comments: use /scrutinize to process and remediate them, then /certify, then git push -u origin HEAD. The /scrutinize round ledger keeps a finding closed in an earlier round from a repeat. The platform's own review (/code-review, the @claude review GitHub flow) is an alternative, described in lore/deep/review.md#platform-surfaces.
9. Merge (if auto-merge is not enabled)
First run the approval check in references/pr-body.md. Merge only when the head commit has the human approvals the Risk tier needs. Otherwise stop and say what is missing.
gh pr merge --squash --delete-branch10. Fix forward (offer)
After the merge, offer a /loop on post-merge CI with AskUserQuestion. On a red run, open a small fix-forward PR through the ship-summary gate. Do not revert unless the fix is unclear. Ship a risky change behind a feature flag. Rules: references/ci-loop.md.
disableGit mode
If disableGit: true: skip the push, PR and merge steps. Commit locally and report done.
Obstacles
When this skill runs as a dispatched unit and something blocks the work, do not wait for a human. Nobody is there. Do not silently ship a degraded result. Return the Obstacles block from lore/obstacles.md with whatever you completed. The fields are STATUS, OBSTACLE, BLOCKER, SEVERITY, WORKAROUND, RECURRENCE, SCOPE, NEXT. Interactively, say the same in prose.
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.

