菜单
Rewrite a feature branch into a clean, reviewable commit stack without changing the final file contents. Use when asked to prepare a PR by resetting existing commits and recomposing the same net changes into small, sequential commits that are easy to review one commit at a time.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | rewrite-pr-history |
| description | Rewrite a feature branch into a clean, reviewable commit stack without changing the final file contents. Use when asked to prepare a PR by resetting existing commits and recomposing the same net changes into small, sequential commits that are easy to review one commit at a time. |
Preserve the exact net file changes while replacing the branch's commit history with smaller, reviewable commits.
current_branch=$(git branch --show-current)
upstream=$(git rev-parse --abbrev-ref --symbolic-full-name @{u} 2>/dev/null || true)
if [ -n "$upstream" ]; then
base_commit=$(git merge-base HEAD "$upstream")
else
base_commit=$(git merge-base HEAD origin/main)
fi
original_head=$(git rev-parse HEAD)
original_tree=$(git rev-parse HEAD^{tree})
backup_tag="backup/rewrite-$(date +%Y%m%d-%H%M%S)"
git tag "$backup_tag" "$original_head"
git reset --soft "$base_commit"
git reset
# Repeat this cycle until done:
# Stage files for the next review unit (method left to the agent)
git diff --cached --stat
git commit -m "<area>: <small, reviewable step>"
git diff --cached --quiet
git diff --quiet
final_tree=$(git rev-parse HEAD^{tree})
[ "$final_tree" = "$original_tree" ]
git range-diff "$base_commit...$backup_tag" "$base_commit...HEAD"
If the rewrite goes wrong, restore the pre-rewrite branch state exactly:
git reset --hard "$backup_tag"
After a successful rewrite and validation, delete the backup tag:
git tag -d "$backup_tag"
When finished, report:
final_tree == original_tree.Run an adversarial two-stage review loop — first a "hate review" subagent (opus by default, fable on request) that tears the changes apart until it signs off, then an OpenAI Codex pass until it signs off too. Use when the user asks to "hate review until it passes", "run the hate reviewer cycle", "hate then codex", or otherwise wants a hostile review gauntlet before merging. Trigger on phrases like "hate reviewer cycle", "hate review loop", "beat this up then codex it".
Review this pull request and pretend you're a senior dev doing a code review and you HATE this implementation.
Commit only your own changes by staging individual hunks via patch, never `git add .` or `git add -A`. Use whenever you are about to stage or commit in a repository that may contain changes from other agents, parallel sessions, or the user working concurrently — which is the default assumption.
Request a code review from Claude Code, implement or evaluate the feedback, and iterate until the review converges. Use when the user asks for a "Claude review", wants feedback from Claude Code, asks for a second opinion from Claude, or wants an iterative review loop between Codex and Claude on the same set of changes.
Request a code review from OpenAI Codex CLI and iterate on the feedback until both agents agree the code is good. Use this skill when the user asks for a "codex review", wants a second opinion from Codex, wants to get feedback on their changes from another AI agent, or wants an iterative review loop. Trigger on phrases like "get a review from codex", "ask codex to review", "codex review", "second opinion", "review from codex", or "have codex look at this".
Use Atlassian CLI `acli` with Jira Cloud to inspect, search, create, edit, assign, comment on, transition, and link Jira work items, and to resolve or run Jira filters by name or ID. Use when the user wants Jira issue operations performed from the terminal instead of the browser, especially for reading issue details, searching with JQL, posting or updating comments, changing status or assignee, editing summaries or descriptions, creating new work items, or running saved filters.