Validate VERIFICATION.md status and create a PR after gates pass.
npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-ship-alo-exp
Please help me install this Agent Skill. Skill: gsd-ship Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/gsd-ship Command: npx skills add https://github.com/alo-exp/silver-bullet --skill gsd-ship-alo-exp
Shipping code without pre-ship verification can lead to untested changes and regressions. This skill automates the gating of pre-ship checks and ensures a PR is created only after verification passes.
Run the ship phase on your current feature branch to push to origin and open a PR only after pre-ship verification passes.
High-intent search queries and answers about installing and using this skill.
Pre-ship verification gates automate the validation of your code before shipping by checking VERIFICATION.md status. This skill enforces guardrails requiring a PASSED status, then pushes your feature branch to origin and creates a PR automatically.
If your VERIFICATION.md status is not PASSED, the pre-ship verification gates will block the workflow. The branch will not be pushed to origin and no PR will be created until the verification requirements are met.
Yes, you can use this to push feature branches and open PRs. After pre-ship verification passes, it pushes the current branch to origin and creates a PR with a standardized conventional title and body.
This pre-ship verification workflow supports both feature branches and release workflows. It coordinates branch push, PR creation, and exit conditions when verification passes, applying automated gating to either scenario.
You need a VERIFICATION.md file to enforce pre-ship verification and prevent untested changes. It serves as the status check gate, requiring a PASSED status to ensure regressions are caught before code is shipped.
The best way to gate code shipping on git feature branches is to automate pre-ship verification by validating a VERIFICATION.md PASSED status. This ensures no untested changes are pushed without passing required guardrails.
rkz91Push a feature branch, create a pull request with an auto-generated body, and track merge status.
LamseyahEliasAutomate GitHub PR lifecycles from branch creation to merge.
Kling0012Automate verification checks with truth scoring and rollback for CI/CD pipelines.
lachiehAutomate base-branch handling, tests, changelog updates, and PR creation for code changes.
