菜单
Smash a GitHub issue end-to-end with Codex: create a feature branch, implement the fix, commit, open a PR, request deep review, wait, and then either fix P1 findings or post a success comment. Use when a user wants a no-nonsense issue execution flow from a GitHub issue URL.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run parallelized deep research across multiple angles. Generate specs, spawn Claude agents in tmux, monitor progress, fix incomplete reports, and compile a styled PDF.
Interact with Kaizen OS via MCP API to manage cards, workitems, scratchpad notes, and calendar events. Use when tasks involve planning, personal productivity, or scheduling.
Generate or edit images via Gemini 3 Pro Image (Nano Banana Pro).
Search the web with Tavily API via curl. Use when users explicitly request Tavily, when you need Tavily-specific controls (search_depth, topic, time_range, include/exclude domains, include_answer, include_raw_content), or when built-in web_search provider setup is unavailable.
Query and update Twenty CRM person records via REST. Use when a task requires finding a person by name, pulling full person data, or updating a person record in Twenty.
| name | codex-smash |
| description | Smash a GitHub issue end-to-end with Codex: create a feature branch, implement the fix, commit, open a PR, request deep review, wait, and then either fix P1 findings or post a success comment. Use when a user wants a no-nonsense issue execution flow from a GitHub issue URL. |
| argument-hint | <github-issue-url> [--team gammawave] [--wait-minutes 15] [--base main] [--no-wait] |
| disable-model-invocation | true |
| allowed-tools | Bash(gh *), Bash(git *), Bash(codex *), Bash(sleep *), Bash(bash *), Read, Grep, Glob |
Run from the repository root:
bash "$(dirname "$0")/scripts/smash.sh" $ARGUMENTS
Default workflow:
main) and create a feature branch.P0/P1 findings remain):P0/P1 findings (next passes), then commit.@codex do a no nonsense deep review of the change for all. Find ALL P0/P1 issues. Explain why each added/exited file is good to go or has issues.--wait-minutes).P0/P1 findings in PR comments and reviews.P0/P1 findings exist, continue the loop from step 2. If no P0/P1 findings exist, post well done boys and exit.Notes:
gh auth login and push permissions.--no-wait or --wait-minutes 0 to skip review monitoring (dry run).