agentleFS
Sign inStart free
deokjinlogdeokjinlog/intent-locked-workflow/skills/finishing-a-development-branch/SKILL.md

finishing-a-development-branch

Skill0 starsChanged 4 months agoMITView on GitHub

Use when implementation is complete and tests pass. Runs the test gate one final time and emits a single termination message; user manually decides merge / PR / keep / discard. (v1.1.14 슬림화 — AskUserQuestion 게이트 + boilerplate 제거)

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时，用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 20 projects that use this

  • kntismSkill

    condition-based-waiting

    Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

    Also in 3 projects that use this

  • MicrosoftSkill

    testing-anti-patterns

    Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

    Also in 4 projects that use this

  • MicrosoftSkill

    root-cause-tracing

    Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

    Also in 5 projects that use this

  • +3 more from Leodorareluctant259

The file

Create a free account to mount
Files
SKILL.md

Finishing a Development Branch (v1.1.14 slim)

implementation 완료 + 모든 테스트 통과 시점에 호출. 1인 개발자가 다음 행동 (merge / PR / keep / discard) 을 이미 알고 있다는 가정 하에, 추가 게이트는 두지 않고 테스트 자동 실행 안전망 + 종료 메시지 만 제공.

Announce at start: "I'm using the finishing-a-development-branch skill to verify tests then emit a termination summary."

When to Use

  • executing-plans / subagent-driven 가 모든 task 완료 후 자동 호출
  • 사용자가 명시적으로 마무리 단계 진입 시 호출

Process

Step 1 — 테스트 자동 실행 (필수 안전망)

자동으로 프로젝트 표준 테스트 명령 실행:

# Python (이 저장소 기본)
source .venv/bin/activate && pytest -v

# 다른 stack 의 경우 README / package.json scripts 확인
  • 모든 테스트 PASS → Step 2 진행
  • FAIL 1건 이상 → 즉시 STOP. 실패한 테스트 출력을 사용자에게 노출 + 한 줄 안내: "❌ 테스트 실패. 마무리 진행 안 함. 실패 원인 확인 후 다시 호출."

이 단계는 유일한 자동 게이트. 깨진 코드가 main / PR 로 흘러 들어가는 것 방지.

Step 2 — 완료 메시지 노출 (한 메시지, 게이트 X)

✅ 모든 task 완료 + 테스트 통과.
   - 변경 commit: <SHA list>
   - RISK 트리거: <카테고리 카운트>
   - 누락/초과: <list 또는 "없음">

마무리하세요. (예: git checkout main && git merge <branch>, 또는 PR 생성, 또는 그대로 두기)

→ AskUserQuestion 게이트 없음. 사용자가 직접 git/gh 명령 실행. boilerplate 자동 생성 X.

Worktree Cleanup (manual)

워크트리 정리는 자동 안 함 (마무리 시점이라고 자동 정리하면 사용자가 "그대로 두기" 의도일 때 자료 손실 가능). 사용자가 직접 처리:

git worktree remove <path>

Anti-Patterns

WrongRight
AskUserQuestion 4-option 게이트 추가게이트 X. 1인 개발자 마찰 회피.
base branch 자동 추정사용자가 본인 브랜치 알고 있음. 추정 시간 낭비.
git/gh boilerplate 자동 생성종료 메시지 한 줄 안내만. 명령 직접 실행.
Step 1 테스트 실패 시 무시NEVER. 유일한 안전망. STOP 강제.

Why slim (v1.1.14)

  • 1인 개발 철학: 사전 verifying-spec + TDD + RISK + 변경이력으로 안전성 분산. 종료 게이트는 중복.
  • v1.1.9~12 게이트 합리화 흐름의 자연스러운 연장 (partial 제거 / fix→no / #12 복원 같은 마찰 정리).
  • discard 안전망 의도적 트레이드오프: 사용자가 직접 git branch -D 시 confirm 없음. 1인 개발자는 git 동작 알고 있음.

Related Skills

  • executing-plans — 인라인 모드 종료 시 호출
  • subagent-driven — 서브에이전트 모드 End-of-Run consolidator 끝 호출

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free