mirror of
https://github.com/obra/superpowers.git
synced 2026-05-01 14:49:06 +08:00
8d9d82bc14
The plugin had a single named agent (`agents/code-reviewer.md`) used by two skills, while every other reviewer/implementer subagent in the repo is dispatched as `general-purpose` with the prompt template living alongside its skill. That asymmetry had no upside and several costs: - Two sources of truth for the code review checklist (the agent file and `requesting-code-review/code-reviewer.md`), both drifting independently. - `Codex` users could not use the named agent directly; the codex-tools reference doc had a workaround section explaining how to flatten the named agent into a `worker` dispatch. - No third-party reliance on `superpowers:code-reviewer` inside this repo. Changes: - Merge `agents/code-reviewer.md` (persona + checklist) and `skills/requesting-code-review/code-reviewer.md` (placeholder template) into a single self-contained Task-dispatch template, matching the shape of `implementer-prompt.md`, `spec-reviewer-prompt.md`, etc. - Update `skills/requesting-code-review/SKILL.md` and `skills/subagent-driven-development/code-quality-reviewer-prompt.md` to dispatch `Task (general-purpose)` instead of the named agent. - Drop the now-obsolete "Named agent dispatch" workaround sections from `codex-tools.md` and `copilot-tools.md` — superpowers no longer ships any named agents, so those instructions documented nothing. - Delete `agents/code-reviewer.md` and the empty `agents/` directory. Tier 3 coverage for the change: a new behavioral test `tests/claude-code/test-requesting-code-review.sh` plants real bugs (SQL injection, plaintext password handling, credential logging) into a tiny project, runs the actual `requesting-code-review` skill against the working tree, and asserts the dispatched reviewer flags every planted issue at Critical/Important severity and refuses to approve the diff. Verified end-to-end on this branch: - The new test passes (5/5 assertions; reviewer caught all planted bugs and several others). - The existing SDD integration test still passes (7/7 subagents dispatched, all as `general-purpose`; spec compliance still rejects extra features; produced code is correct). - Session JSONLs confirm zero remaining `superpowers:code-reviewer` dispatches anywhere in the SDD pipeline.
1.8 KiB
1.8 KiB
Copilot CLI Tool Mapping
Skills use Claude Code tool names. When you encounter these in a skill, use your platform equivalent:
| Skill references | Copilot CLI equivalent |
|---|---|
Read (file reading) |
view |
Write (file creation) |
create |
Edit (file editing) |
edit |
Bash (run commands) |
bash |
Grep (search file content) |
grep |
Glob (search files by name) |
glob |
Skill tool (invoke a skill) |
skill |
WebFetch |
web_fetch |
Task tool (dispatch subagent) |
task with agent_type: "general-purpose" or "explore" |
Multiple Task calls (parallel) |
Multiple task calls |
| Task status/output | read_agent, list_agents |
TodoWrite (task tracking) |
sql with built-in todos table |
WebSearch |
No equivalent — use web_fetch with a search engine URL |
EnterPlanMode / ExitPlanMode |
No equivalent — stay in the main session |
Async shell sessions
Copilot CLI supports persistent async shell sessions, which have no direct Claude Code equivalent:
| Tool | Purpose |
|---|---|
bash with async: true |
Start a long-running command in the background |
write_bash |
Send input to a running async session |
read_bash |
Read output from an async session |
stop_bash |
Terminate an async session |
list_bash |
List all active shell sessions |
Additional Copilot CLI tools
| Tool | Purpose |
|---|---|
store_memory |
Persist facts about the codebase for future sessions |
report_intent |
Update the UI status line with current intent |
sql |
Query the session's SQLite database (todos, metadata) |
fetch_copilot_cli_documentation |
Look up Copilot CLI documentation |
GitHub MCP tools (github-mcp-server-*) |
Native GitHub API access (issues, PRs, code search) |