Enter the worktree of a GitHub PR, validate the code-review comments raised on it against what the code actually does and the repo rules, fix the valid ones directly in the PR's source/tests, and report in chat — a brief note per closed comment and a detailed plain-language explanation of every comment left unclosed…
Validate review findings about an implementation plan against the codebase and repo rules, fix the valid ones in the plan, and write a feedback file noting what changed and what was rejected (and why). For plan-review findings, not code-review findings.
TRIGGER CONDITIONS - invoke this skill when ANY of these apply: User-triggered (explicit request): User mentions "specification", "SPEC", "SPEC.md", "spec requirements" User asks to "verify with spec", "confirm with specification", "check requirements" User requests "authoritative requirements" or "source of truth"…
Export the survived comments from a completed implementation-plan review into a timestamped Markdown findings artifact. Use when the user asks to save, write, or export plan-review comments/findings under .ai/implplans/PLANID/findings/REVIEWTIMESTAMP/finding.md while preserving the original review wording and wrapping…
Use this skill whenever you are about to run any write gh CLI command — gh pr edit, gh pr create, gh issue edit, gh issue create, gh pr comment, gh issue comment, gh pr close, gh pr merge, gh release create, or similar. High-level gh commands sometimes fail with "missing required scopes" auth errors even though the…
Expert review of an implementation plan against a GitHub issue/enhancement description (provided as a local file or a GitHub issue URL) and the current repository codebase. Use when asked to critique a plan for correctness, completeness, codebase alignment, risks, and test/rollout readiness (do not implement).
Critically review a GitHub issue plus a "described changes" overview written by a developer — open the referenced code, verify the overview's claims against what the code actually does, and report gaps, inconsistencies, and likely mistakes — without modifying any files. Invoke manually.
Manually review a feedback file produced after implementation-plan review findings were addressed. Use when the user asks to verify that plan changes correctly close, correctly reject, or fail to close the original findings, while checking for newly introduced or newly exposed problems. Independently adjudicates only…
Use this skill WHENEVER you are about to run the integration tests of this project — the whole suite, a single module, or one test. This includes any time you would otherwise type pytest -m integration, uv run pytest -m integration, run anything under tests/integration/, or want to check live…
Use this skill whenever the agent needs to deploy a smart contract to Sepolia testnet via Foundry (forge create or forge script --broadcast), routed through the Blockscout PRO API's JSON-RPC gateway instead of a third-party RPC provider. Trigger on requests like "deploy this contract to Sepolia", "deploy via Foundry"…
Use when user asks to "run tool as function", "test directly", or "call standalone" (outside MCP server). Essential for correct mock Context setup (MagicMock + AsyncMock). Finds integration tests with real test data.
Use to implement EXACTLY ONE phase of a structured implementation plan, or to fix ONE Final-Checklist item. Invoked by the implement-plan orchestrator. Follows the phase's detailed spec — Files to Modify, Implementation Details, Unit Tests, and Verification — without straying into other phases. Does not commit; the…
Use to verify that ONE phase of a structured implementation plan was implemented completely and honestly. Invoked by the implement-plan orchestrator after a phase-developer finishes a phase (and after each fix round). Checks correspondence between the plan's phase steps and the actual changes — catches skipped…
Runs before the agent uses a tool for Bash tool calls, executing ensure-python-venv.sh and enforce-integration-runner.sh (2 commands). From blockscout/mcp-server.
Use to implement a structured implementation plan (e.g. temp/implplans/issue-.md) phase by phase. Trigger when the user asks to implement, execute, realize, or "do" an implementation-plan file. Orchestrates a phase-developer subagent and a plan-correspondence-verifier subagent for each phase, commits each verified…
You are a senior Python developer. Your area of expertise is to build MCP (Model Context Protocol) servers to build a communication between an LLM-based products and large data sources accessible by REST API.