with one click
speq-code-tools
Semantic code navigation and editing triggered by speq-skills.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Semantic code navigation and editing triggered by speq-skills.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit a speq project's health — spec-library structure, feature/decision-log/plan validation, mission-to-spec sync, unrecorded plans, and gitignore hygiene — then guide fixes. Use when the user asks to audit, health-check, doctor, lint, or sanity-check the specs or repo, or after cloning or inheriting a speq project.
Code review tag taxonomy and findings output format — guardrail violations, dead code, obsolete tests, bad comments, optimizations, YAGNI/over-engineering. Triggered by code-reviewer.
Headless follow-up to speq-plan-pr. Continues on a plan's feat/plan-name branch, runs speq-implement, bumps the version, runs the real test suites, records only if green, then pushes and opens/updates a PR. Arg: plan name, PR number, or branch name.
Orchestrate implementation of reviewed plans according to the spec deltas. Arg: <plan-name>.
Create specs/mission.md via interactive interview. Detects brownfield vs greenfield.
Headless, non-interactive version of speq-plan. Plans a feature without a live interview, commits the result to a feat/plan-name branch, and opens a PR. If a decision genuinely needs a human, it persists the partial plan and open questions and asks in a PR comment instead of blocking. Arg — plan name, feature intent text, PR number, or branch name.
| name | speq-code-tools |
| description | Semantic code navigation and editing triggered by speq-skills. |
Semantic code navigation and editing via Serena MCP.
| Task | Use | Not |
|---|---|---|
| List directory | list_dir | ls, find |
| Find files | find_file | find, rg --files |
| File symbols | get_symbols_overview | rg "class|function" |
| Symbol definition | find_symbol | rg "function foo" |
| Symbol references | find_referencing_symbols | rg "foo(" |
| Update function | replace_symbol_body | read/edit/write |
| Insert after | insert_after_symbol | read/edit/write |
| Insert before | insert_before_symbol | read/edit/write |
| Rename symbol | rename_symbol | rg + manual edits |
Apply the Feynman Technique — explain your understanding before proceeding. Call these tools at key moments:
| Tool | When |
|---|---|
think_about_collected_information | After exploration sequence |
think_about_task_adherence | Before writing code |
think_about_whether_you_are_done | Before reporting completion |
Explore → find_symbol, get_symbols_overview
Understand → find_referencing_symbols
Reflect → think_about_collected_information
Edit → replace_symbol_body, insert_*_symbol
Verify → find_referencing_symbols
Complete → think_about_whether_you_are_done