Gate code changes through Definition of Done, reviews, and automated tests before opening a PR.
npx skills add https://github.com/tale-project/tale --skill ship-tale-project
Please help me install this Agent Skill. Skill: ship Source: https://github.com/tale-project/tale/tree/main/.claude/skills/ship Command: npx skills add https://github.com/tale-project/tale --skill ship-tale-project
The pre-PR routine ensures that code changes are thoroughly vetted, meet the Definition of Done, and pass all required gates before a PR is opened, preventing incomplete or brittle merges.
Invoke the ship routine after completing a change to gate the work and open a conventional-commit PR.
High-intent search queries and answers about installing and using this skill.
Automate pre-merge code review gates by orchestrating changes through a Definition of Done, self-review, lint checks, and tests before opening a conventional-commit PR. This enforces a standardized gate ensuring only vetted, release-ready code is merged.
A Definition of Done workflow for merge-ready PRs validates code changes through formatting, linting, type checks, migrations, tests, and accessibility checks. It requires explicit steps like walking a Ripple Map to ensure all release criteria are met before PR creation.
Ensure atomic commits and a checklist in automated PRs by running an end-to-end pre-merge pipeline that generates a conventional-commit PR. The pipeline enforces atomic commit structures and automatically embeds a verification checklist in the PR body.
Yes, you can run migrations and accessibility checks as part of an automated PR gate. The standardized gate validates formatting, linting, type checks, cross-locale documentation, accessibility checks, and tests to verify release readiness before merging.
You need to walk a Ripple Map before creating a pull request when gating code changes through a Definition of Done. It is an explicit step in the pre-merge workflow to verify behaviour and ensure all impacts of the code change are validated.
Standardize code review gates across documentation and test changes by applying an end-to-end pre-merge pipeline. This orchestrates lint, test, and cross-locale documentation verification gates, ensuring any code change merged through a standardized gate is release-ready.
pingmepiSynthesize approved MVP artifacts into release horizons and decision gates.
mdmagnuson-creatorMerge target branches into source branches and resolve pull request conflicts.
Ramprasad4121Prepare codebases for security review with static analysis and documentation.
lookatitudeAutomate CI/CD pipeline design with multi-stage workflows and gate matrices.
