Results for “build-fix”

Diagnoses and fixes build, type, and runtime errors with minimal changes, covering TypeScript, PyTorch, and other build systems.

Diagnose and fix slow MSBuild incremental builds by identifying why targets re-execute unnecessarily, covering common causes like missing Inputs/Outputs, volatile properties, and FileWrites registration.

Require fresh evidence before claiming an implementation, fix, build, or test is complete.

Builds auditable firm-fixed-price IGCEs using BLS wages, layered fringe, overhead, G&A and profit, GSA CALC+ positioning, and GSA Per Diem travel data.

Watch, audit, and fix another agent's work by reconstructing the original request, inspecting evidence, and reporting gaps.

Executes commands, inspects git state, debugs CI or builds, makes narrow fixes, and reports exactly what changed and what was verified.

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

Runs a structured bug-fix pipeline that scouts, diagnoses, fixes, reviews, and finalizes code changes with optional quality re-verification.

Runs a structured bug-fix pipeline: scouts evidence, diagnoses root cause, applies minimal fixes, and reviews before committing.

Systematically repair a broken feature or module by scoping, tracing dependencies, diagnosing all issues, fixing them in order, and verifying end-to-end.

Begins a hotfix for a production issue using git-flow. This skill should be used when the user asks to "start a hotfix", "create hotfix branch", "fix a critical bug", "git flow hotfix start", or wants to begin a hotfix. Accepts either an explicit version or a natural-language description of the fix.

Responding to incidents: identifies impact scope, formulates recovery procedures, creates postmortems. Use when incident response or disaster recovery is needed. Delegates fixes to Builder.

Structured workflow to reproduce, diagnose, plan, fix, verify, and record a bug fix, requiring a deterministic reproduction before diagnosis and minimal changes only.

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

When reviewing code, generate the complete corrected version — not just the issues, but the exact fixed code ready to copy-paste.

Unified developer workflow for fixing bugs. Analyzes issue-tracker context, cross-checks docs/code, proposes a solution, implements the fix, verifies locally, and delivers a PR/MR.

Reviews and repairs risky or unclear code with minimal validated changes, running a fixed-point loop until the diff is clean across two consecutive review cycles.

Fixes one security finding with the smallest safe patch, regression coverage, and verification.

Use when the user asks to fix, debug, or make a specific feature/module/area work end-to-end. Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken', 'focus on [area]'. Not for quick single-bug fixes — this is for systematic deep-dive repair across all files and dependencies.

Diagnose and repair failing CI for an existing pull request without reopening the implementation pipeline.

Verify fix commits address audit findings without new bugs

Verify fix commits address audit findings without new bugs

Transform an approved video script into a Remotion build specification with scaffolded project directory, compositions, scene components, and render config

Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.

Generate one high-value follow-up workflow proposal when MoonMind execution quality issues are detected in a run.

>-