원클릭으로 Manus에서 모든 스킬 실행

post-merge-checks

스타3

포크2

업데이트2026년 7월 4일 09:47

Housekeeping after a PR merges — delete the local branch, pull main, remove resolved blockers from draft PRs and issues, and check whether the parent epic can close. Run whenever a PR has been merged.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ChrisKlug

ChrisKlug/zeekayda-auth

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Post PR-Merge Checks

Run this whenever a PR has been merged. This skill is the single source of truth for the post-merge flow.

Steps

1. Clean up local state

The merge has likely deleted the remote branch. Delete the local branch and any worktree that was used for it.

Then prune stale agent worktrees so they don't accumulate:

Run git worktree prune.
Run git worktree list and check every worktree under .claude/worktrees/:
- If git -C <path> status --porcelain shows changes, leave it alone and report it to the user.
- Otherwise, if its branch is merged into main (check with git branch --merged main) or its branch no longer has an open PR, remove it with git worktree remove <path> and delete the branch with git branch -d <branch>.
Report anything you left in place and why.

2. Update main

git checkout main
git pull --ff-only

Always do this so new work never starts from a stale main.

3. Resolve blockers

Note the merged PR number and any issue numbers it closes (e.g. Closes #N in the PR body).
Search all open draft PRs for a ## Blockers section referencing the merged PR number or any closed issue number.
For each matching PR, remove that blocker entry from the PR body.
If a PR has no remaining blockers after removal, mark it ready for review (gh pr ready).
Issues use native blocked-by relations, which resolve automatically when the blocking issue closes — no cleanup needed. But check whether any issue just became fully unblocked (gh api /repos/OWNER/REPO/issues/N/dependencies/blocked_by on issues that listed a closed issue as a blocker) and report newly actionable issues to the user.

4. Check the parent epic

For each closed issue, check whether it is a sub-issue of a type:epic. If so, query all sub-issues of that epic. If every sub-issue is now closed, ask the user whether to close the epic.

이 저장소의 다른 Skills

같은 저장소

check-code-coverage

ChrisKlug/zeekayda-auth

Compare test coverage on the current branch against main and fail if it regressed. Run before opening any PR — CI enforces a coverage regression gate, and this catches it locally first.

2026-07-103

code-navigation

ChrisKlug/zeekayda-auth

LSP-first code navigation for ZeeKayDa.Auth — load the LSP tool up front and use it for all symbol-level lookups. Applies to every agent that reads or writes C# in this repository.

2026-07-093

check-formatting

ChrisKlug/zeekayda-auth

Verify and fix code formatting with dotnet format. Run before opening any PR, and whenever formatting errors are reported by CI or the Stop hook.

2026-07-063

write-issue

ChrisKlug/zeekayda-auth

Write a well-structured GitHub issue for ZeeKayDa.Auth — decides between an ADR issue and an implementation issue, applies the issue templates, hierarchy, and labels, and links sub-issues to their epic. Use when fleshing out a new idea, filing a bug, creating design or implementation issues, or triaging incoming issues.

2026-07-043

review-branch

ChrisKlug/zeekayda-auth

Set up a git worktree for reviewing or auditing a branch or PR so the review runs against the right code. Use before any code review, audit, or acceptance-criteria verification that targets a branch other than the currently checked-out one.

2026-07-043

security-checklist

ChrisKlug/zeekayda-auth

Security review checklist for ZeeKayDa.Auth. Apply to every change touching tokens, cryptography, endpoints, or storage — during security review, and as a developer self-check before opening a PR that touches those areas.

2026-07-043

name	post-merge-checks
description	Housekeeping after a PR merges — delete the local branch, pull main, remove resolved blockers from draft PRs and issues, and check whether the parent epic can close. Run whenever a PR has been merged.
allowed-tools	["Bash(git )","Bash(gh )"]

Post PR-Merge Checks

Run this whenever a PR has been merged. This skill is the single source of truth for the post-merge flow.

Steps

1. Clean up local state

The merge has likely deleted the remote branch. Delete the local branch and any worktree that was used for it.

Then prune stale agent worktrees so they don't accumulate:

Run git worktree prune.
Run git worktree list and check every worktree under .claude/worktrees/:
- If git -C <path> status --porcelain shows changes, leave it alone and report it to the user.
- Otherwise, if its branch is merged into main (check with git branch --merged main) or its branch no longer has an open PR, remove it with git worktree remove <path> and delete the branch with git branch -d <branch>.
Report anything you left in place and why.

2. Update main

git checkout main
git pull --ff-only

Always do this so new work never starts from a stale main.

3. Resolve blockers

Note the merged PR number and any issue numbers it closes (e.g. Closes #N in the PR body).
Search all open draft PRs for a ## Blockers section referencing the merged PR number or any closed issue number.
For each matching PR, remove that blocker entry from the PR body.
If a PR has no remaining blockers after removal, mark it ready for review (gh pr ready).
Issues use native blocked-by relations, which resolve automatically when the blocking issue closes — no cleanup needed. But check whether any issue just became fully unblocked (gh api /repos/OWNER/REPO/issues/N/dependencies/blocked_by on issues that listed a closed issue as a blocker) and report newly actionable issues to the user.

4. Check the parent epic

For each closed issue, check whether it is a sub-issue of a type:epic. If so, query all sub-issues of that epic. If every sub-issue is now closed, ask the user whether to close the epic.