From shipyard
Configures Shipyard by detecting CI/CD platforms, deployment targets, container configs, and DevOps tools; generates .claude/shipyard.json and queries Context7 for CI/CD docs. Run once per project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/shipyard:configureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Configure Shipyard by detecting CI/CD platforms, deployment targets, container configs, and available DevOps tooling.
Configure Shipyard by detecting CI/CD platforms, deployment targets, container configs, and available DevOps tooling.
Load each step through the fetch command (handles caching, decryption, and auth):
"~/.composure/bin/composure-fetch.mjs" skill shipyard configure {step-filename}
Do NOT read cache files directly — they are encrypted at rest. Always use the fetch command above.
| # | File |
|---|---|
| 1 | 01-detect-stack.md |
| 2 | 02-detect-platform.md |
| 3 | 03-detect-tools.md |
| 4 | 04-context7-queries.md |
| 5 | 05-config-and-report.md |
npx claudepluginhub hrconsultnj/claude-plugins --plugin shipyardManages DevOps tasks: audits CI/CD pipelines for issues, builds production Dockerfiles, sets up deployments, maps pipelines, builds CI/CD from scratch, and ships code via PRs.
Designs and implements CI/CD pipelines, GitOps workflows, and zero-downtime deployments with rollback and observability.
Generates CI/CD workflows for GitHub Actions, GitLab CI, or Bitbucket Pipelines from detected project stack. Includes lint, typecheck, test, build, deploy stages with caching, concurrency, and least-privilege permissions.