shipyard
CLAUDE.md66 starsChanged 5 months agoMITView on GitHub
Claude Code plugin (v4.5.0) for structured project execution: idea → brainstorm → plan → build → ship. Four files must have matching version numbers. scripts/check-versions.sh enforces this (also runs in pre-commit hook and CI).
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- code-simplificationSkill
- documentationSkill
- git-workflowSkill
- import-spec-fileSkill
- import-specSkill
- infrastructure-validationSkill
- lessons-learnedSkill
- parallel-dispatchSkill
- security-auditSkill
- shipyard-brainstormingSkill
- shipyard-debuggingSkill
- shipyard-executing-plansSkill
- shipyard-handoffSkill
- shipyard-tddSkill
- shipyard-testingSkill
- shipyard-verificationSkill
- shipyard-writing-plansSkill
- shipyard-writing-skillsSkill
- using-shipyardSkill
The file
Files
Shipyard
Claude Code plugin (v4.5.0) for structured project execution: idea → brainstorm → plan → build → ship.
Commands
npm test # Full BATS test suite
npm run test:fast # Unit tests only (bats --filter-tags unit)
npm run test:ci # Parallel execution (4 jobs)
bash scripts/check-versions.sh # Verify version sync across files
shellcheck --severity=warning scripts/*.sh hooks/*.sh test/run.shArchitecture
commands/ 27 slash commands (markdown + YAML frontmatter)
skills/ 19 auto-activating skills (skills/<name>/SKILL.md)
agents/ 10 specialized agents (markdown + YAML frontmatter)
scripts/ State management, version checks, cleanup utilities
hooks/ Plugin lifecycle hooks (SessionStart, TeammateIdle, TaskCompleted, Stop)
test/ BATS test suite + test_helper.bash
docs/ Protocols, guides, state schema, context engineering
.claude-plugin/ Plugin metadata (plugin.json, marketplace.json)
.husky/ Pre-commit: check-versions.sh && npm testVersion Sync
Four files must have matching version numbers. scripts/check-versions.sh enforces this (also runs in pre-commit hook and CI).
package.json.claude-plugin/plugin.json.claude-plugin/marketplace.jsonCHANGELOG.md(top entry)
Conventions
- Files/dirs: kebab-case
- Commits: conventional format —
feat:,fix:,chore:,build:,shipyard(phase-N): - Bash scripts:
set -euo pipefail, ShellCheck compliant (--severity=warning) - Skills: auto-discovered from
skills/*/SKILL.md— no manual registration - Agents: model values are
opus,sonnet,haiku, orinherit - Adding components: see CONTRIBUTING.md
Gotchas
- Pre-commit hook runs
check-versions.sh && npm test— both must pass .shipyard/is gitignored — local project state only, never committed- jq >= 1.6 required —
state-read.shexits code 3 if missing - Symlinked
.shipyard/is rejected (prevents writes outside project) - Team locking uses directory-based locks at
${TMPDIR}/shipyard-state-${hash}.lock - CI matrix tests on macOS, Ubuntu, and Windows (WSL); ShellCheck + version check run on Ubuntu only
- PR version bump enforced — CI rejects PRs where package.json version <= main branch version
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.

