review-and-ship
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
- License 许可
- Apache-2.0
- 所属仓库
- stigmer/stigmer
- 最近更新
- 2026-11-14
- Stars
- ★ 9
- Forks
- 6
01 前言 Front Matter
- name
- review-and-ship
- description
- Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
03 SKILL.md 正文
Review and ship
Trigger
Reviewing changes before shipping. Close key issues, verify behavior, and open or update a PR.
Workflow
- Gather context: diff against base branch, uncommitted changes, recent commits, changed files, and user intent from recent relevant chats if useful.
- Run targeted tests for changed behavior. If no focused tests exist, decide whether to add them or document the gap.
- Review for correctness, regressions, security, and intent fit. Use parallel subagents for larger diffs.
- Fix critical issues before finalizing and re-run affected tests.
- Commit selective files with a concise message.
- Push branch and open or update a PR.
Suggested Checks
git fetch origin main
git diff origin/main...HEAD
git status
gh pr checks --json name,bucket,state,workflow,link
Guardrails
- Prioritize correctness, security, and regressions over style-only comments.
- Keep commits focused and avoid unrelated file changes.
- If pre-commit checks fail, fix the issues rather than bypassing hooks.
- Use
gh pr checksinstead of GitHub Actions-only commands when judging PR readiness.
Output
- Findings summary (critical, warning, note)
- Tests run and outcomes
- PR URL
04 同仓库更多 Skills
writing-hookify-rules
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
sql-migrations
Write safe database schema migrations - reversible steps, online index builds, and backfills in batches.
repo-conventions
How to change Go code in this repository - error wrapping, table-driven tests, doc comments, no new dependencies, and running go test before finishing.
incident-postmortem
Write a blameless incident postmortem - timeline, impact, root cause, contributing factors and follow-up actions with owners.
data-analysis
Summarise a data export or table - lead with the key finding and give every number its baseline or comparison.
customer-support
Answer customer questions about orders, returns and refunds from the written policies and the order system, ending with a clear next step.