Menu
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
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ê.
Use when you have a written implementation plan to execute
Spreadsheet toolkit. Reach for it whenever the artifact on either side of the conversation is a workbook file — .xlsx, .xlsm, .xltx, .csv, .tsv — and the user wants that artifact produced, changed, cleaned, or read. Typical triggers: 'build me a model', 'update this sheet', 'add a column', 'compute the totals as formulas', 'sanity-check this xlsx', 'export sheet 2 to CSV', 'render the workbook as PDF', 'the spreadsheet in ~/Downloads is a mess, fix it'. Applies equally to financial models, ops reports, data cleanups, and template fills. Skip it when the workbook is only source material and the real output is a Word doc, an HTML page, a Python script that runs standalone, a Google Sheets integration, or an ingestion pipeline into a database — in those cases the spreadsheet is a means, not the deliverable.
Perform a focused, evidence-based code review. Use when the user asks to review code, a diff, pull request, branch, commit, or implementation before merging.
Smart git commit message generator following Conventional Commits. Use when the user says 'commit', 'commit this', 'write a commit message', 'smart commit', or asks to create a git commit.
Use when the user asks what OpenZeroCode can do, how a feature works (memory, checkpoints, agents, subagents, tasks, compose, learn), how to configure it, where config/data lives, which config key controls a behavior, what CLI or slash commands exist, or how to enable/disable/tune something — the self-documenting reference for OpenZeroCode itself.
Use when executing implementation plans with independent tasks in the current session
Baseado na classificação ocupacional SOC
| name | compose:merge |
| description | Use when implementation is complete, all tests pass, and you need to decide how to integrate the work |
Guide completion of development work by presenting clear options.
Before presenting options, verify tests pass:
npm test
If tests fail: Stop. Don't proceed until tests pass.
Normal repo:
git checkout main
git pull
git merge <feature-branch>
git branch -d <feature-branch>
git push -u origin <feature-branch>
gh pr create --title "<title>" --body "Summary of changes"
Report: "Keeping branch ."
Confirm first:
git branch -D <feature-branch>