build

Included with Lifetime

$97 forever

Use when the user says "build X", "implement X", "create X feature" or hands a spec and expects working code. Spec-first, evidence-gated, test-as-acceptance. Refuses to start coding before alignment on what success looks like.

Code Review

What this skill does


# build

Spec → tests → code → verify → docs. Refuses to skip steps.

## Method

1. **Spec alignment.** If spec is ambiguous, surface 1-3 ambiguities **before any code**. One round of clarification, then proceed. If spec is missing, draft it from user input and confirm in &lt; 100 words.
2. **Memory pass.** `mem_search { query: <feature topic>, k: 8 }`. If prior decisions exist, cite them. If they conflict with spec, flag — do not silently override.
3. **Acceptance criteria.** Before writing any code, write the test names that would prove this works. List as bullet checklist. User confirms or amends.
4. **Plan.** Use native CC `Plan` agent. Output: file list, order, risk register, rollback path. ≤ 200 words.
5. **Build.** Implement smallest slice that lights up acceptance criterion #1. Run test. Green → criterion #2. Loop.
6. **Verify.** Run full suite. Run lint, typecheck. Read your own diff.
7. **Docs.** Update README/changelog/inline docs **only** for user-visible changes. Don't doc internal implementation details.

## Output shape

End-of-build summary:

```
Spec:        <one line>
Acceptance:  ✓ N/M criteria passing
Files:       <list>
Tests:       <list of new tests, with paths>
Verify:      lint ✓ types ✓ tests ✓
Rollback:    <git command if reverting>
Memory:      captured <summary count> events
Next:        <suggested follow-up or "complete">
```

## Rules

- Never write code before acceptance criteria are confirmed.
- Never skip the test-first step — even for "trivial" changes (trivial is where bugs hide).
- Never expand scope beyond spec. Out-of-scope ideas → log to memory + suggest as `/siftcoder:ideate` topic.
- Never delete tests to make a build pass.

## Anti-patterns

- Writing code, then writing tests to match the code (false safety)
- Mocking the thing under test (test does nothing)
- "Should work" without running it
- Touching unrelated files in the same change

## When NOT to use

- Bug fixes — use `/siftcoder:fix`
- Refactors with no new behaviour — use `/siftcoder:refactor`
- One-line typo fixes — just do it
- Investigation only (no code) — use `/siftcoder:investigate`

## Subagent dispatch

- `Plan` for the design step
- `general-purpose` for multi-file coordinated implementation
- `Explore` for codebase mapping when entering unfamiliar areas
- `tester` agent (if installed) for behaviour-coverage test gen, not just line coverage

Files: 1

Size: 2.6 KB

Complexity: 7/100

Category: Code Review

Source: https://github.com/ialameh/sift-coder/tree/main/skills/coding/build

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts