qa-cycle
免费QA + bugfix cycle until it passes
中文简介正在准备中。当前显示原文说明。
79 个 · 按相关度排序
QA + bugfix cycle until it passes
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
中文简介正在准备中。当前显示原文说明。
Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
中文简介正在准备中。当前显示原文说明。
Use when a change is small and already understood - at most three files, such as a typo, a config value, a rename, or a one-line bugfix - and a plan file would cost more than the change
中文简介正在准备中。当前显示原文说明。
Use when implementing any feature or bugfix, before writing implementation code
中文简介正在准备中。当前显示原文说明。
Code implementation, refactoring, and bugfixes for create-vue-dsfr. Use for implementing features, refactoring code, or fixing bugs. Read the shared project skill before acting.
中文简介正在准备中。当前显示原文说明。
Code implementation, refactoring, and bugfixes. USE FOR: implementing features; refactoring code; fixing bugs; modifying existing code. DO NOT USE FOR: writing tests (separate skill); documentation (separate skill); commit conventions (separate skill).
中文简介正在准备中。当前显示原文说明。