evergonlabsevergonlabs/aiframework/.claude/skills/aiframework-ship/SKILL.md

aiframework-ship

Skill0 starsChanged 7 months agoMITView on GitHub

aiframework shipping workflow. Runs lint + test + build, reviews code, checks invariants, updates docs + changelog, commits. NEVER pushes without explicit approval.

In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aif-analyzeSkill
- aif-enhanceSkill
- aif-evolveSkill
- aif-feedbackSkill
- aif-ingestSkill
- aif-learnSkill
- aif-pulseSkill
- aiframework-learnSkill
- aiframework-reviewSkill
- aif-readySkill
- aif-researchSkill
- aif-reviewSkill
- aif-shipSkill
- aif-statusSkill
- retroSkill
- sheal-askSkill
- sheal-checkSkill
- sheal-driftSkill
- sheal-retroSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Check changed files against all invariants in CLAUDE.md.
line 29
Distinctive:
Update any documentation affected by the changes.
line 32
Distinctive:
Update CHANGELOG.md with user-facing description
line 35
Very specific:
Update vault/memory/status.md with shipping details
line 43
Very specific:
If significant architectural decision was made → create ADR in vault/memory/decisions/
line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

/aiframework-ship — Shipping Workflow

Step 1: Verify

cd rust && cargo clippy
cd rust && cargo check
make test

Step 2: Invariant Scan

Check changed files against all invariants in CLAUDE.md.

Step 3: Doc Sync

Update any documentation affected by the changes.

Step 4: CHANGELOG + VERSION bump

Update CHANGELOG.md with user-facing description
Bump VERSION (PATCH=fix, MINOR=feature, MAJOR=breaking)

Step 5: Commit (NEVER push without asking the user)

Step 5.5: Vault Update

If vault/ exists:

Update vault/memory/status.md with shipping details
If significant architectural decision was made → create ADR in vault/memory/decisions/
Run vault/.vault/scripts/vault-tools.sh lint

Step 6: Report

Output a summary table:

Step	Status	Details
Lint	PASS/FAIL	...
Type check	PASS/FAIL	...
Tests	PASS/FAIL	X passed, Y failed
Build	PASS/FAIL	...
Invariants	PASS/FAIL	...
Docs	SYNCED/NEEDS UPDATE	...
Changelog	UPDATED	...
Committed	YES/NO	commit hash

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free