Generate conventional commits, enforce rebase-merge, and create gated PRs.
npx skills add https://github.com/mathiasbourgoin/roster --skill roster-ship
Please help me install this Agent Skill. Skill: roster-ship Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/roster-ship Command: npx skills add https://github.com/mathiasbourgoin/roster --skill roster-ship
Manually managing code shipping steps like commit formatting, rebasing, PR creation, and quality gate checks is error-prone and inconsistent, especially for coordinated agent development pipelines where skipped reviews or incorrect merge strategies can introduce critical defects.
Use the roster-ship skill to ship the current task's implementation branch to main via a rebase-merged PR once review and QA gates are approved.
High-intent search queries and answers about installing and using this skill.
You can enforce conventional commits and gated PRs by automating commit generation, applying rebase-merge workflows, and requiring explicit human approval before pushing code or merging. This ensures implementation work passes review and QA gates before reaching the main branch.
Rebase-merge workflow enforcement matters because it strictly prohibits merge commits and squash merges, ensuring a linear, clean git history. This eliminates inconsistent merge strategies that can obscure commit logs and introduce defects in coordinated development pipelines.
Automated conventional commit generation creates standardized, lowercase imperative commit messages directly from implementation briefs. This eliminates manual formatting errors and ensures commit history consistency across the entire pipeline orchestration process.
Yes, gated PR creation requires mandatory human approval and passing review and QA gates before any code push or PR merge occurs. This applies specifically to Roster pipeline framework workflows where validation steps must not be skipped.
The best way to ship code safely is to automate the entire workflow using conventional commit generation, strict rebase-merge enforcement, and gated PR creation. This guarantees all quality checks pass and human approval is secured before merging to the main branch.
Yes, the gated PR workflow supports optional knowledge base synchronization post-ship. After a rebase-merged PR passes review and QA gates, you can synchronize your knowledge base to maintain documentation accuracy alongside code changes.
ravnhqRewrite feature branch history into clean conventional commits with backup branches.
flurdyRebase a feature branch onto main after a parent PR merges.
vasilyu1983Design Git branching strategies, PR workflows, and release automation.
HsnSaboorOrganize staged changes into atomic commits with conventional messages.
