What is build-incremental?

A step-by-step coding workflow that builds a feature in small pieces and checks each piece as it goes. It detects the project's tools and can run type checks, code-style checks, and tests.

Use it when implementing a feature, milestone, or other multi-part coding task. It can build, verify, fix reported errors, and optionally create a commit for each completed unit.

It catches errors close to where they are introduced instead of leaving all checks until the end. It also helps keep multi-step implementation work organized.

build-incremental — Skill for Claude Code by mostafa-drz

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add mostafa-drz/claude-skills --skill build-incremental

Clone the repo

git clone --depth 1 https://github.com/mostafa-drz/claude-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/build-incremental/github.svg)](https://agentmods.dev/skills/mostafa-drz/claude-skills/build-incremental)

Your own site

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/build-incremental"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/build-incremental/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/build-incremental"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/build-incremental.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,612 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00060	$0.01612
Opus 5	$0.00030	$0.00806
Sonnet 5	$0.00012	$0.00322
Haiku 4.5	$0.00006	$0.00161

Measured 10d ago against content hash 6fac417987ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

build-incremental scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

code/build-incremental/SKILL.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build

Implement code in progressive, verified increments. Each unit is built, checked, and committed before moving to the next.

Preferences

Read ~/.claude/skills/build-incremental/preferences.md using the Read tool. If not found, no preferences are set.

Project context

On startup, use Bash to detect: project stack files (ls package.json Cargo.toml pyproject.toml go.mod Makefile), CLAUDE.md presence, current git branch, and git status. Skip any that fail.

Command routing

Check $ARGUMENTS:

help → display help then stop
config → interactive setup then stop
reset → delete ~/.claude/skills/build-incremental/preferences.md, confirm, stop
--dry-run <description> → show the plan without executing then stop
--no-commit <description> → build and verify but don't commit
--skip-lint <description> → skip linting, only run type checks
anything else → proceed with build

Help

Build — Implement code in verified increments

Usage:
  /build-incremental <what to build>             Build incrementally with checks + commits
  /build-incremental --dry-run <description>     Show plan without executing
  /build-incremental --no-commit <description>   Build and verify, don't commit
  /build-incremental --skip-lint <description>   Skip lint, only typecheck
  /build-incremental config                      Set toolchain and commit preferences
  /build-incremental reset                       Clear preferences
  /build-incremental help                        This help

Examples:
  /build-incremental add user settings page with form validation
  /build-incremental Milestone 2 from IMPLEMENTATION_PLAN.md
  /build-incremental --dry-run refactor auth middleware

How it works:
  1. Detects your toolchain (or reads from preferences)
  2. Breaks work into committable units
  3. For each unit: implement → check → fix → commit
  4. Reports summary with all commits

Current preferences:
  (shown above under Preferences)

Read the full file on GitHub · 186 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 186 lines · 60 tokens per session scan A 6fac417987ae

Subscribe to this mod's changes

build-incremental is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed 28d ago), licensed MIT. It adds 60 tokens to every session and 1,612 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Git and workflow Testing ai-tools automation claude claude-skills developer-tools

quick-finalize

Close out a change without the deep review loop: stage, simplify code and docs, run the project's checks, smoke test, update the changelog, self-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the…

tobihagemann/turbo · 89 tokens

test-fixing

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

mhattingpete/claude-skills-marketplace · 44 tokens

git-pushing

Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.

mhattingpete/claude-skills-marketplace · 70 tokens

alpha-forge-preship

Alpha Forge quality gates for PR review - RNG determinism, URL validation, parameter validation, manifest sync.

terrylica/cc-skills · 27 tokens

iterate

Diverge-converge workflow: spin up N agents on isolated worktrees, each exploring a different approach to the same problem. Compare results side-by-side (with optional preview ports), pick a winner, merge it back. Use when the user says /iterate, 'try multiple approaches', 'explore different directions', or wants to…

SZoloth/skill-pack · 73 tokens

ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is…

Ertinox7711/SGRR-AGI-V2 · 105 tokens