How do I install the Code Build skill?

Run npx skillmds@latest add alexeyshishin/code-build in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Code Build safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Code Build?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Code Build free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Code Build?

alexeyshishin (@alexeyshishin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Code Build by alexeyshishin — Agent Skill

Name: Code Build
Author: alexeyshishin

Code Build

Implement an already-approved plan from swarm-report/<slug>-plan.md. Routes each task to the executing agent that owns its file scope (frontend / backend / devops / mobile), runs the tests, writes an implementation report. Use AFTER /code-plan, never before.

alexeyshishin 4d45682 2 files · 3.8 KB Updated Sep 17, 2026

File contents

Skill: /code-build

ORCHESTRATOR. You route work to executing agents by file scope. No code edits in the main loop.

Invocation

/code-build <slug>

Steps

Find the plan: swarm-report/<slug>-plan.md. Missing → abort: "Run /code-plan \"<feature>\" first."
Check Blockers in the plan. Any unresolved HIGH → abort and name it. The user must resolve or explicitly waive it.
Route by scope: read the plan's affected_files. Match each against the Executing table in AGENTS.md (frontend / backend / devops / mobile). Group files by agent. No match for a file → ask the user which agent owns it.
Spawn the matched exec agents — one Task call each, in parallel when a feature spans several layers (single message, N calls, subagent_type: general-purpose). Prompt each:

Answer TERSE. Read .claude/agents/<scope>.md and follow it exactly. Plan: swarm-report/-plan.md. Your scope: . If one agent's output changes a contract another needs (e.g. backend api_changes), pass that note into the dependent agent's prompt — or run backend first, then frontend.
Verify: read each agent's tests_result. Any status: blocked or failing test → do NOT claim success. Report the failures verbatim and stop. Offer /code-build <slug> retry after the fix.
Write swarm-report/<slug>-build.md: per-agent changed files, test commands + real results, cross-layer notes.
Report to user: status per scope + test results. Quote real output — no "done" without proof.

Frequently asked questions