Results for “fix”

QA cycling workflow - test, verify, fix, repeat until goal met

Diagnoses and fixes failing installed skills by reading the SKILL.md and error output, classifying the failure, applying the smallest fix, and attaching a verification recipe.

PROACTIVE SKILL — automatically apply whenever writing, generating, or editing any text that is mainly in Chinese. No user trigger needed. Also use when the user explicitly asks to "fix Chinese", "修改中文", "去翻译腔", "去AI味", "fix Chinese formatting", or "review Chinese text". Eliminates AI-sounding expressions and translation artifacts. Enforces Chinese-English mixed formatting rules (spacing, punctuation, bold formatting).

Validates generated SRS documents against IEEE 830-1998, fixing errors and reporting warnings.

Meta-skill workflow orchestrator for bug investigation and resolution. Routes to debug, implement, test, and commit based on scope.

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

Validates generated SRS documents against IEEE 830-1998, fixes errors, and reports compliance verdict.

Persists through implement-verify-fix loops until a task is fully completed and verified, overriding default stopping behavior.

CEO/Dispatcher. Owner-facing mission intake, CXX meeting orchestration, event routing, and final Owner reports. Trigger with /goal, /submission, /hot-fix, /ceo.

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire document.

Provides a structured debugging workflow for non-technical founders, covering reproduction, diagnostic gathering, and AI-assisted fixes.

Sends and reads email for your own domain through a local mail server using fixed scripts, and creates new mail accounts.

Embody the Taoist sage Zhuangzi to dissolve fixed perspectives, reframe uselessness, and guide spontaneous action through parables and paradox.

Diagnose bugs, failing tests, or unexpected behavior by reproducing, isolating, hypothesizing with evidence, and confirming fixes before making changes.

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

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.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Transforms AI-generated text into authentic, human-sounding writing by detecting AI patterns, fixing rhythm, and injecting brand voice.

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

Diagnoses WSL2 and Cursor/Claude performance issues on Windows, including memory, swap, disk, caches, and configuration, then recommends safe fixes.

Audits an Obsidian wiki for structural issues like orphaned pages, broken wikilinks, stale content, and provenance drift, with optional automated fixes.

Runs commands, inspects git state, debugs CI failures, and makes narrow fixes with exact proof of what was executed and verified.

Runs meetings effectively: classifies meeting types, prepares agendas, facilitates discussions, captures decisions and actions, and audits recurring meetings to fix poor meeting culture.

Executes terminal commands, inspects git state, debugs CI or builds, and makes narrow fixes with exact proof of what was executed and verified.

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.

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.

Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.

Enforces a disciplined Red-Green-Refactor (TDD) workflow in TypeScript/Node.js. Use this whenever creating new features, fixing bugs, or migrating logic to ensure high-quality, verifiable implementations.

Diagnoses whether a draft will resonate with its audience using a five-dimension communication psychology framework, identifies structural problems, and gives specific fixes.

Runs an adversarial, decision-aware review of all session work before committing, checking decision adherence and code maintainability, and applies only user-authorized fixes.