Results for “feature-repair”

Use when paired-end reads need to be reordered so mates appear consecutively, or when preparing BAM files for featureCounts by adding dummy reads for singletons.

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

Repairs failed task verification by choosing a strategy: retry with adjustments, decompose into sub-tasks, prune infeasible tasks, or escalate to the user.

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.

Autonomously repairs failed task verification by choosing retry, decompose, prune, or escalate strategies before surfacing to the user.

Update or correct an existing skill file based on judge feedback or improved understanding.

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

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.

通用多轮迭代改进：对任意研究制品反复调用 /review → 解析反馈 → 修复 → 更新 wiki，直到达标

Re-render a hero image into aspect ratios for Instagram, TikTok, YouTube Shorts, and Twitter/X.

Review git diffs or file scopes for code reuse, quality, efficiency, and clarity issues, then optionally apply safe, behavior-preserving fixes.

Inspects a skill's SKILL.md and its observations/runs.md log, identifies failure patterns, and proposes a targeted amendment to improve the skill. Trigger on: "improve this skill", "fix this skill", "update this skill", "why does X keep failing", "this skill is wrong", "add this to the skill", or automatically when observations/<skill-name>/runs.md contains 3 or more failure entries. Outputs the amendment as a diff the user can review before applying. Records the amendment rationale in observations/<skill-name>/runs.md after user confirmation.

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist and attack surface mapping.

Guides a structured feature-development workflow: explore the codebase with subagents, draft a plan for approval, implement step by step, verify with parallel checks, and record conventions.

Processes a PR's review comments (Copilot or human), classifies them, applies the fixes that belong, replies to each thread, and pushes. Use whenever the user says "address the review", "fix what Copilot said", "handle the comments", mentions Copilot already reviewed a PR, or passes a PR number/URL with pending reviews — or in Spanish "revisá los comentarios", "arreglá lo que dijo Copilot", "atendé el review".

Identify underspecified areas in the current feature spec by asking targeted clarification questions and encoding answers back into the spec.

Generates specific, implementable fixes for each vulnerability finding, producing code patches, configuration changes, dependency updates, and IaC fixes with before/after code and verification steps.

BDD spec authoring — create, update, or delete .feature files following best practices

Reproduce a bug as a failing regression test, fix until green, review, and commit via a delegated pipeline.

Implements feature flags and remote configuration in Flutter apps using Firebase Remote Config and LaunchDarkly, enabling staged rollouts, A/B testing, and kill switches without app updates.

Diagnose and remove FPS caps so the editor and game run uncapped (or at a target FPS). Use when the user says the editor/game is "locked", "capped", or "stuck" at a frame rate (commonly 60 FPS), asks to "unlock"/"uncap"/"raise" FPS, or wants to set a max FPS. Covers t.MaxFPS, VSync, fixed/smoothed frame rate, and background CPU throttling (EngineSettingsService).

Plan before implementing - understand scope and approach with detailed guidance

Investigate and fix bugs, crashes, null references, and runtime errors in QuizVerse.

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

Autonomous iOS bug fixer. (gstack)

Fixes all lint errors and formatting issues automatically