fin
Fin
Overview
Finish a PR end-to-end: push updates, watch checks, squash-merge, and clean up state.
Workflow
-
Identify the PR and target branch.
- Use
gh pr view(current branch) orgh pr listto locate it.
- Use
-
Update the PR.
- Ensure the branch is up to date, run required checks, and push:
git status, fix issues, thengit push.
- Ensure the branch is up to date, run required checks, and push:
-
Monitor checks until green.
- Use
gh pr checks --watchorgh run watch <run-id>. - If checks fail, fix, push, and re-watch.
- Use
-
Squash-merge the PR.
- Prefer
gh pr merge --squash --delete-branchunless repo policy dictates otherwise. - If approvals are missing, request them before merging.
- Prefer
-
Clean up local state.
- Fetch the updated mainline, switch to it, and delete the merged branch.
Guardrails
- Do not merge if required checks or approvals are missing.
- Keep the merge method aligned with repo policy.
- If any step is blocked, state the blocker and required next action.
More from tkersey/dotfiles
grill-me
>
99complexity-mitigator
Mitigate incidental complexity in existing code when control flow is tangled, nesting is deep, names are hard to parse, or reasoning requires cross-file hops. Use when a review stalls on readability, you need an analysis-first refactor plan before edits, or you want essential-vs-incidental verdicts, dominant-risk triage, ranked simplification steps, one visibility artifact, and a TRACE assessment. Do not use for greenfield requirements discovery, architecture selection, or delivery planning.
59creative-problem-solver
Lateral-thinking playbook that always returns a five-tier strategy portfolio (Quick Win through Moonshot). Use when you need options, alternatives, or trade-offs; when progress is stalled or failing repeatedly; or when you ask to think creatively, reframe constraints, and choose a strategic path before execution.
59mesh
Use `$mesh` for homogeneous leaf-batch execution over `spawn_agents_on_csv`: once planning has shaped repeated independent units, prefer one substantive row per unit with structured results and explicit concurrency.
47web-browser
Use when tasks need real-browser web automation in Chrome/Chromium via CDP: open or navigate URLs, click/type/select in forms, run page JS, wait for selectors, scrape structured content, capture screenshots, validate UI flows, or run measured web-browser latency checks (`bench:eval`, `bench:all`) for perf regressions.
43invariant-ace
Turn 'should never happen' into 'cannot happen' by defining owned inductive invariants and enforcing them at parse/construct/API/DB/lock/txn boundaries with a verification signal. Use when prompts mention invariants, impossible states, validation sprawl, cache/index drift, idempotency/versioning, retries/duplicates/out-of-order events, race/linearization bugs, loop correctness, or hardening another implementation workflow with invariant checks first.
31