Results for “build-fix”

Automatically detects project state and runs an 8-phase pipeline to plan, build, test, lint, fix bugs, and document code across multiple AI coding agents.

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

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.

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

Systematic workflow for verifying bug fixes to ensure quality and prevent regres...

Detects and fixes common MSBuild anti-patterns in .csproj, .vbproj, .fsproj, .props, .targets, and .proj files, covering Exec misuse, unquoted conditions, hardcoded paths, and more.

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Use when the user says "task:", "fix:", "todo:", "log task:", "log fix:", "run task:", "run fix:", or asks to log, run, list, or manage project tasks. Also use when asked to generate or update a changelog from completed tasks.

Implement bounded remaining work for an issue-driven repository change after an authoritative verifier reports concrete gaps. Use when a workflow supplies an issue brief or assessment plus materialized gate-result and remaining-work evidence, and the existing candidate must be corrected without creating a MoonSpec feature packet.

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

Shape, bet, and build products using the 37signals philosophy from Getting Real, Rework, and Shape Up — fix time, flex scope, and ship with small autonomous teams.

Repo housekeeping: sync READMEs to match current architecture, remove dead files (logs, screenshots, deprecated code, build artifacts), update npm/pip/cargo dependencies to latest. Use when asked to: "housekeep", "clean up repo", "update README", "update dependencies", "fix vulnerabilities", "remove dead code", "tidy.

Use when a task is well-defined, has an automatic way to verify success (tests, linter, build), and is tedious or large enough to benefit from unattended iteration - e.g. "get all tests passing", "implement this spec end to end", "fix every lint error". Not for one-shot changes or work that needs human judgment mid-stream.