fin_skill

This skill finalizes a GitHub PR end-to-end by updating branches, monitoring checks, squash-merging, and cleaning local/remote state.
  • Python

42

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill tkersey/dotfiles --skill fin

  • SKILL.md1.2 KB

Overview

This skill finalizes GitHub pull requests end-to-end: it updates the branch, monitors CI until checks pass, performs a squash-merge, and cleans up both remote and local state. It automates the checklist you follow when asked to finish, land, merge, or close a PR. Use it to ensure merges respect required checks and repo policies while keeping your local repository tidy.

How this skill works

The skill locates the PR (current branch or from a list), ensures the branch is up to date, and pushes any last changes. It then watches CI checks or specific workflow runs until they turn green, prompting for fixes if they fail. Once checks and approvals satisfy repo rules, it performs a squash-merge and deletes the feature branch remotely, then fetches and syncs your local mainline and removes the local branch.

When to use it

  • You are ready to land a feature and need to finish the PR end-to-end.
  • You want to push final fixes, watch CI until green, and then merge automatically.
  • You need to perform a squash-merge and delete the branch in one flow.
  • You want to ensure required checks and approvals are present before merging.
  • You need local repository cleanup after a merge.

Best practices

  • Identify the correct PR using gh pr view or gh pr list before taking action.
  • Do not merge until required checks and approvals are green; state blockers if present.
  • Prefer gh pr merge --squash --delete-branch unless repository policy requires a different merge method.
  • When checks fail, fix locally, run git status, then git push and re-watch the checks.
  • After merging, fetch and switch to the mainline branch, then delete the merged local branch to avoid drift.

Example use cases

  • Finish a current-branch PR: update, watch checks, squash-merge, and delete branch in one command sequence.
  • Recover a PR where CI failed: apply a fix, push, and resume watching until green before merging.
  • Merge a long-running feature branch once approvals and checks are satisfied, ensuring repo policy compliance.
  • Clean up local and remote branches after a successful merge to keep the repo tidy.

FAQ

Do not merge. Report the failing checks, apply fixes or request necessary changes, push updates, and re-watch until checks pass.

Can the merge method be changed?

Yes—use the repository's policy as the source of truth. The default preferred method is squash; switch to merge or rebase if policy requires it.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational