Results for “fix-review-cycle”

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

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

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

Automates the cycle of fixing CI failures, addressing PR review feedback, and pushing changes until all checks pass.

Runs five parallel review agents on code changes, validates findings, triages them, and applies approved fixes after confirmation.

Runs a QA validation cycle followed by bugfix until all criteria pass clean, with automated verification and re-validation.

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

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

阶段⑤ Review。审查已实现的代码并修复问题。

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

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".

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.

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

コード品質改善の全サイクルを実行するスキル。品質スイープ→コードレビュー→Issue化→自律実装ループ→完了通知の5フェーズ。ユーザーが「dev-cycle」「開発サイクル」「品質改善」「自律ループ」などと言った時、または /dev-cycle を呼び出した時にトリガーする。

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

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

>-

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

Systematic debugging — reproduce, read the error, isolate, hypothesize, fix, verify, document. Use when tracking down a bug, unexpected behavior, or test failure — including phrases like "this doesn't work", "why is this failing", or "help me debug".

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

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

Reviews lockfiles, installers, provenance, CI permissions, dependency confusion, artifacts, registries, and publishing.

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

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to ma...

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

Use when reviewing a branch, PR, or work-in-progress changes against standards and spec

Run tests and systematically fix all failing tests using smart error grouping. Use when user asks to fix failing tests, mentions test failures, runs test suite and failures occur, or requests to make tests pass.

Waits for Copilot to review a PR and automatically chains the fix-comments cycle, up to two rounds. Use right after opening a PR with `ship`, and whenever the user says "wait for the review", "let me know when Copilot answers", "keep going with the PR", or asks to leave the PR review cycle running — or in Spanish "quedate esperando el review", "avisame cuando Copilot conteste", "seguí vos con el PR".