القائمة
Use when implementation is complete and the user wants to commit, push, publish, preserve, or clean up the branch. Handles branch-finish decisions, explicit commit-and-push requests, and concise next-step handoff after the work has been saved.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use Strata, the Legacy Code Labs macOS visual-spec app, through its local Streamable HTTP MCP server. Trigger when Codex needs to create, read, validate, update, version, diff, or restore Strata diagrams; build visual specs from user flows, discovery trees, architecture sketches, or D2; diagnose Strata MCP setup; or verify a feature against a shared Strata canvas.
Use Clarity, the LegacyCodeHQ structural design CLI, for dependency impact graphs, architecture/refactoring verification, before-commit design checks, code review context, cycle/module/workspace exploration, AGENTS.md Clarity setup, or rebuilding/probing Clarity command availability. Use when Codex needs to run or interpret clarity show, watch, languages, extensions, modules, cycles, workspace, setup, or version-specific Clarity commands.
Plan, build, harden, and review Kotlin backend services with Spring Boot, Ktor, coroutines, typed configuration, persistence, migrations, testing, security, resilience, and operations. Use for Kotlin HTTP APIs, workers, service refactors, production-readiness reviews, or JVM backend architecture decisions.
Reliability-first Kotlin skill for implementing, refactoring, or reviewing Kotlin libraries, CLIs, JVM modules, shared domain code, coroutine code, and Java interop boundaries. Use when work needs null-safety discipline, value and sealed types, idiomatic scope-function use, typed errors, structured concurrency, testing, or JVM quality gates.
Reliability-first Python skill for implementing, refactoring, or reviewing Python packages, CLIs, services, scripts, async code, tests, and typed modules. Use when work needs type hints, dataclasses, boundary parsing, exception design, context managers, asyncio cancellation, packaging, pytest or unittest strategy, ruff, mypy, pyright, or runtime safety.
Analyze images using local Ollama vision model (qwen3.5:4b) with automatic pre-resizing and filename sanitization for reliable processing.
| name | finishing-a-development-branch |
| description | Use when implementation is complete and the user wants to commit, push, publish, preserve, or clean up the branch. Handles branch-finish decisions, explicit commit-and-push requests, and concise next-step handoff after the work has been saved. |
Guide completion of development work by verifying quality, saving the work intentionally, and leaving the next move clear.
Core principle: verify first -> save intentionally -> execute the chosen path -> leave a clean runway.
commit, push, open a PR, keep this branch, or discard, execute that path after verification.origin.If the user already knows what they want, do not force an option menu first.
Examples:
commit and push to originopen a draft PRsave this progress and keep goingdiscard this branchExecute the requested path directly once verification is complete and any destructive action is confirmed.
When the user has not chosen, present exactly these options:
Implementation complete. What would you like to do?
1. Merge back locally
2. Push and create a Pull Request
3. Keep the branch as-is
4. Discard this work
verification-before-completion when the repo has multiple verification gates.