sealmindset/Ship It
Guided delivery skill that helps new developers ship code to production through simple yes/no questions — no DevOps knowledge required.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | GitHub token for API access (PR creation, labels, status checks) | yes | ${{ github.token }} |
| mode | How the skill was triggered. "interactive" for CLI Q&A, "ci" for automated PR pipeline behavior. | no | ci |
| intent | Override intent classification. Only used in CI mode when the label is already applied. One of: experiment, shareable, prod-ready. | no | "" |
| dev-environment | GitHub environment name for dev deployments. | no | dev |
| prod-environment | GitHub environment name for production deployments (should have required reviewers configured). | no | production |
| working-directory | Directory to run the skill in. Defaults to repo root. | no | . |
| arguments | Arguments passed from /ship-it command (e.g., "save" for save mode). | no | "" |
Outputs
| name | description |
|---|---|
| intent | The classified intent: experiment, shareable, or prod-ready |
| pr-url | URL of the created or updated pull request |
| pr-number | Number of the created or updated pull request |
| blockers-found | Whether hard blockers were detected (true/false) |
| blocker-summary | Plain-language summary of any blockers found |
| deploy-target | Where the artifact should deploy based on intent: none, dev, or dev+prod |