Automate commit, push, and state transition for gated story shipping.
npx skills add https://github.com/ramontramontini/CTEDemo --skill ship-ramontramontini
Please help me install this Agent Skill. Skill: ship Source: https://github.com/ramontramontini/CTEDemo/tree/main/.claude/skills/ship Command: npx skills add https://github.com/ramontramontini/CTEDemo --skill ship-ramontramontini
Ship a story by performing the final commit, push, and state transition within a gated workflow. It ensures all quality work (tests, docs, compliance, drift, ship-review) is completed in /pull Step 4 before invoking /ship.
Provide a STORYID to ship after verifying in_progress status and the review_ship stamp, then monitor the push and final transition steps.
High-intent search queries and answers about installing and using this skill.
Automating git commit, push, and state transition requires a gated workflow that validates pre-flight checks and formal approvals before final execution. The process ensures all quality work like tests and compliance is completed, then performs the final push to transition the story to done.
A gated workflow for shipping software stories is a formalized process enforcing quality checks and stamp validation before allowing a final code push. It ensures tasks like ship-review and compliance are verified, preventing incomplete work from transitioning to a done state.
Yes, shipping a story in a gated deployment requires a formal review_ship stamp and in_progress status verification. Pre-flight readiness checks validate the presence of these required stamps and fields before allowing the commit and push sequence to execute.
The best way to ensure quality checks before pushing a deployment is using a structured pre-flight validation process. This approach reconciles tasks, validates required gate stamps, and confirms that all tests and documentation are finished prior to the final commit.
Gated pull requests fail readiness checks when required pre-flight validations detect missing gate stamps, incomplete quality tasks, or invalid in_progress status. The workflow performs structured error handling to prevent pushing code that lacks the necessary formal approvals.
Yes, you can use API interactions via hub-client.sh for task reconciliation during a git deployment workflow. These API calls align quality work with shipping requirements, verify in_progress states, and facilitate the final gated transitions after passing readiness checks.
arbgjrEvaluate SDLC quality gates for artifacts, criteria, and approvals.
ramontramontiniExecute downstream stories from ready_to_pull to done with enforced gates.
joeylife94Automate code deployment with branch detection, tests, version bump, and pull request creation.
vtgiang-dotcomBlock Git commits and pushes that use --no-verify to bypass pre-commit hooks.
