القائمة
Review one VFloat AFK workflow issue after implementation. Use when an issue is ready-for-review and needs diff review, acceptance validation, follow-up issue creation, or completion.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill when creating, updating, reviewing, or syncing VFloat documentation in docs/api or docs/guide, especially after source changes in src/composables/ or when the user asks for VFloat API pages, guides, tutorials, doc fixes, or docs review feedback even if they do not name the docs folders directly.
Coordinate VFloat's markdown-based AFK issue workflow. Use when creating, assigning, implementing, reviewing, committing, or monitoring .scratch PRD and issue files across Codex or other markdown-capable agents.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Prepare final validation and Conventional Commit proposals for completed VFloat AFK workflow work. Use when all feature issues are completed or a PRD is ready-to-commit.
Implement one VFloat .scratch issue from the AFK workflow. Use when an agent is assigned a ready-for-agent issue, must update Work Log and Validation Log, and should move it to ready-for-review.
| name | issue-reviewer |
| description | Review one VFloat AFK workflow issue after implementation. Use when an issue is ready-for-review and needs diff review, acceptance validation, follow-up issue creation, or completion. |
Use this skill to review exactly one Status: ready-for-review issue.
Read:
AGENTS.md.agents/workflows/afk-issue-loop.mdUse a code-review stance. Prioritize:
Avoid broad refactors unless they are required for the issue to be correct.
If the work is acceptable:
Review Notes with what was checked.Status: completed.If follow-up work is needed:
Status: ready-for-agent, Category, Parent,
Blocked by, acceptance criteria, and an agent brief.Review Notes.Status: review-blocked.Do not silently fix substantial issues during review. Make review findings durable so any agent can pick them up.