finishing-a-development-branch
Complete feature development with structured options for merge, PR, or cleanup
Discover Development skills, compare source repositories and read the instructions for each workflow.
Complete feature development with structured options for merge, PR, or cleanup
Refactor with tests first, one change at a time, never mix refactoring with bug fixes or new features
TDD for process documentation - test with subagents before writing, iterate until bulletproof
Never test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.
Validate at every layer data passes through to make bugs impossible
Replace arbitrary timeouts with condition polling for reliable async tests
Write the test first, watch it fail, write minimal code to pass
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Check all external inputs for validity - garbage in, nothing out, never garbage out
Maintain skills wiki health - check links, naming, cross-references, and coverage
Write comments explaining WHAT and WHY, never temporal context or history
Lightweight, git-native issue tracking (aka beads) for AI agents. Use for creating, planning, updating, and tracking issues with dependencies. Invoke when user mentions tbd, beads, to-do lists, planning, tracki...
Guides architectural decisions for Deep Agents applications. Use when deciding between Deep Agents vs alternatives, choosing backend strategies, designing subagent systems, or selecting middleware approaches.
Guides architectural decisions for LangGraph applications. Use when deciding between LangGraph vs alternatives, choosing state management strategies, designing multi-agent systems, or selecting persistence and...
Go concurrency patterns for high-throughput web applications including worker pools, rate limiting, race detection, and safe shared state management. Use when implementing background task processing, rate limit...
Write Architectural Decision Records following MADR template. Applies Definition of Done criteria, marks gaps for later completion. Use when generating ADR documents from extracted decisions.
Extract architectural decisions from conversations. Identifies problem-solution pairs, trade-off discussions, and explicit choices. Use when analyzing session transcripts for ADR generation.
Pinia Store 架構規範。Use when creating app/stores/**/*.ts files, working with defineStore, managing global state, or building Pinia stores. Always use this skill for store design patterns, naming conventions,...
Clarify ambiguous requests by researching first, then asking only judgment calls; stop before implementation.
Create micro-commits (minimal incision) with at least one validation signal per commit.
Generate iterative `plan-N.md` files in the repo root (max N=5). Use only when asked; clarify before `plan-1.md`; stop at `plan-5.md`.
Preflight bead work: verify beads are in use, confirm explicit start/continue, identify active bead or select next `bd ready`, clarify done criteria, and scope audit before marking `in_progress`.
bd (beads) issue-tracking workflow; use when `.beads/` exists or when running `bd` commands.
TRACE (Type/Readability/Atomic/Cognitive/Essential) lens for explaining code and proposing improvements (no edits applied).
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.