development-branch-closeout

Estrelas12

Forks1

Atualizado26 de maio de 2026 às 10:08

Use after implementation and required verification when PM/coordinator must choose merge, pull request, preserve, discard, or workspace cleanup handling for the current branch.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

funky-eyes

funky-eyes/best-copilot

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	development-branch-closeout
description	Use after implementation and required verification when PM/coordinator must choose merge, pull request, preserve, discard, or workspace cleanup handling for the current branch.

Development Branch Closeout

Use this after required reviews and verification have evidence. It turns branch handling into an explicit, safe PM decision.

Preconditions

Required implementation, review, and verification evidence is present or explicitly blocked.
Current branch, worktree state, base branch, and dirty status are known.
Top-level session or PM/coordinator owns the user-facing decision.

Detect

git status --short
git branch --show-current
git rev-parse --git-dir
git rev-parse --git-common-dir
git rev-parse --show-toplevel
Candidate base: main, master, or PM-provided base branch.

Decision Surface

Use native ask UI when available. Follow the Native Ask Contract from core-workflow-contract for structured ask UI requirements. Present only applicable options:

merge_local: merge to the selected base branch after verification on the merge result.
open_pr: push the branch and create a pull request; preserve the worktree for review follow-up.
keep_branch: leave branch/worktree as-is and report path, branch, and next manual command.
discard: destructive path; requires explicit typed confirmation and a list of commits/files/worktree path that would be removed.

If native ask UI is unavailable and a choice is required, follow the Native Ask Contract from core-workflow-contract for fallback behavior.

Safety Rules

Do not merge, push, delete, or discard unless the user explicitly chose that action.
Do not offer merge/PR as complete when verification is failed or blocked.
Cleanup only worktrees known to be project-created, such as under .worktrees/, worktrees/, or a workspace-isolation artifact. Never remove harness-owned or unknown workspaces.
For open_pr and keep_branch, preserve the worktree.
For discard, require exact typed confirmation before deleting anything.

Output

Return:

branch_state
base_branch
dirty_status
verification_summary
decision_options
selected_action
cleanup_scope
residual_risk

Mais deste repositório

mesmo repositório

core-workflow-contract

funky-eyes/best-copilot

Use when an agent needs the shared best-copilot contract for source priority, runtime adapters, init gates, work modes, dispatch packets, review, verification, memory, spec, state persistence, or closeout.

2026-07-1512

repo-init-manual-fallback

funky-eyes/best-copilot

Use inside repo-init-scan after the official stage whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed.

2026-07-1512

senior-project-expert-workflow

funky-eyes/best-copilot

Use when coordinating large, ambiguous, cross-module, multi-agent, planning, dispatch, fan-in, closeout, or workflow-evolution work as the Senior Project Expert.

2026-07-1512

specification-writer-workflow

funky-eyes/best-copilot

Use when maintaining requirements, design, tasks, ADRs, execution-plan state, closeout records, or memory/spec recovery as the Specification Writer.

2026-07-1512

subagent-driven-development

funky-eyes/best-copilot

Use when an approved tasks.md from a Spec Bundle, or a compact approved small-work plan, should be executed by fresh-context specialist subagents, with each task receiving implementation, spec-compliance review, code-quality review, and verification before closure. DO NOT USE FOR: missing plans, brainstorming, or simple single-file edits.

2026-07-1512

target-spec-bootstrap

funky-eyes/best-copilot

Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.

2026-07-1512

Development Branch Closeout

Use this after required reviews and verification have evidence. It turns branch handling into an explicit, safe PM decision.

Preconditions

Required implementation, review, and verification evidence is present or explicitly blocked.

Current branch, worktree state, base branch, and dirty status are known.

Top-level session or PM/coordinator owns the user-facing decision.

Detect

git status --short

git branch --show-current

git rev-parse --git-dir

git rev-parse --git-common-dir

git rev-parse --show-toplevel

Candidate base: main, master, or PM-provided base branch.

Decision Surface

Use native ask UI when available. Follow the Native Ask Contract from core-workflow-contract for structured ask UI requirements. Present only applicable options:

merge_local: merge to the selected base branch after verification on the merge result.

open_pr: push the branch and create a pull request; preserve the worktree for review follow-up.

keep_branch: leave branch/worktree as-is and report path, branch, and next manual command.

discard: destructive path; requires explicit typed confirmation and a list of commits/files/worktree path that would be removed.

If native ask UI is unavailable and a choice is required, follow the Native Ask Contract from core-workflow-contract for fallback behavior.

Safety Rules

Do not merge, push, delete, or discard unless the user explicitly chose that action.

Do not offer merge/PR as complete when verification is failed or blocked.

Cleanup only worktrees known to be project-created, such as under .worktrees/, worktrees/, or a workspace-isolation artifact. Never remove harness-owned or unknown workspaces.

For open_pr and keep_branch, preserve the worktree.

For discard, require exact typed confirmation before deleting anything.

Output

Return:

branch_state

base_branch

dirty_status

verification_summary

decision_options

selected_action

cleanup_scope

residual_risk