All authors
Claude Skills by NYTC69
github.com/NYTC6915 skills0 installs22 views
- ExecuteLegacy execute skill (legacy workflow (removed from routing in v2.13.0; deleted in v2.13.1)). Use only when the user explicitly names the legacy execute skill; an existing plan or a review of existing code otherwise goes to review-loop. Codex Stage 1 execute skill. Run the execution + quality polish + delivery stages of review-loop against one of three entry modes: resume an approved session (`--session`), execute a user-supplied plan (`--plan`), or run a pure-CR pass on the current working t...Votes: 0GitHub stars: 3
- GuideCodex Stage 1 guide for review-loop and the shared Claude/Codex state model.Votes: 0GitHub stars: 3
- PlanLegacy plan skill (legacy workflow (removed from routing in v2.13.0; deleted in v2.13.1)). Use only when the user explicitly names the legacy plan skill; a plan request otherwise goes to review-loop or paired-session. Codex Stage 1 planning-only skill. Drives a work item from raw description to a reviewer-approved plan in `.review-loop/sessions/{uuid}.md`, then exits with a hint to resume via `review-loop:execute --session UUID`. Use when you want plan-only iteration without immediately enter...Votes: 0GitHub stars: 3
- Review LoopCodex-native Stage 1 review-loop skill. Orchestrates planning and execution with a Codex Executor and Claude/Codex reviewer backends while sharing the .review-loop protocol with Claude Code.Votes: 0GitHub stars: 3
- Code Quality LoopIterative review-fix loop on the uncommitted change: reviews, fixes, simplifies and consolidates tests, as a paired-session review-only run (`run --review-only`). The legacy loop was removed in v2.13.0: `entry: legacy`, `--legacy` and `--reorganize` are refused.Votes: 0GitHub stars: 3
- ReorganizeReorganize code file structure: rearrange modules, extract reuse, remove redundancy, add section comments. Preserves all functionality and logic.Votes: 0GitHub stars: 3
- Review PrComprehensive code review using specialized agents. Each agent focuses on a different quality aspect (code, errors, comments, types, tests, simplify). It runs the paired-session report mode (a PR, a ref or the local change; no writer, nothing posted); the legacy review was removed in v2.13.0, so `entry: legacy` and `--legacy` are refused.Votes: 0GitHub stars: 3
- ExecuteLegacy workflow (removed from routing in v2.13.0; deleted in v2.13.1): run only when the user names /review-loop:execute. An existing plan or a review of existing code goes to /review-loop. Run the execution + quality polish + delivery stages of review-loop against one of three entry modes: resume an approved session (`--session`), execute a user-supplied plan (`--plan`), or run a pure-CR pass on the current working tree (`--review-only`). Supports batched runs via `--stop-after STAGE`. Use w...Votes: 0GitHub stars: 3
- GuideShow review-loop usage guide: how it works, commands, configuration, and key features. Use when the user asks for help with review-loop.Votes: 0GitHub stars: 3
- PlanLegacy workflow (removed from routing in v2.13.0; deleted in v2.13.1): run only when the user names /review-loop:plan. For plan-only work use /review-loop:paired-session --plan-only. Run the planning phase only: drive a work item from raw description to a reviewer-approved plan in `.review-loop/sessions/{uuid}.md`, then exit with a hint to resume via `review-loop:execute --session UUID`. Use when you want plan-only iteration without immediately entering execution.Votes: 0GitHub stars: 3
- Review LoopAutomates a Plan-Execute-Review workflow with built-in iteration loops. An Orchestrator coordinates an Executor sub-agent and a configurable Reviewer (external AI CLI like Codex, or Claude sub-agent) to drive work items from description to delivery — with every review finding visible to the user. Trigger: "run review-loop on", "start review loop", "let the agents handle", or any task the user wants driven by a plan→review→implement→CR cycle.Votes: 0GitHub stars: 3
- Paired SessionUse in exactly four cases - the user explicitly asks for paired-session, the review-loop entry hands off because .review-loop/config.md sets `entry: paired-session`, the review-loop entry hands off because that key is absent or invalid (the default entry), or the review-pr skill hands off on its paired route; this is the plan, implementation, independent-review, finish, polish, docs, security and acceptance workflow. Generic review-loop requests go to the review-loop entry first, which routes...Votes: 0GitHub stars: 3
- LegacyExplicit control command: run the existing legacy review-loop workflow on a work item, ignoring the `entry` config key. Trigger only when the user names `/review-loop:legacy`. Do not trigger on a bare review-loop request.Votes: 0GitHub stars: 3
- Paired SessionDrive an implementation through the paired-session coordinator: independent PLAN review, EXEC implementation/review, adversarial gate, then finish, quality polish, docs and security up to operator acceptance. Trigger in exactly five cases: (1) the user explicitly asks for paired-session or names this explicit coordinator entry; (2) the review-loop entry hands off because .review-loop/config.md sets `entry: paired-session`; (3) the review-loop entry hands off because that key is absent or inva...Votes: 0GitHub stars: 3
- Review PrReview a GitHub pull request ("review PR 123", a PR URL) or a named branch or ref and write a review report, the review-loop review-pr; also when the user explicitly asks for review-pr. A general request to review local changes ("review my changes") is not this skill (review-loop). It runs the paired-session report mode (no writer, nothing committed or posted); the legacy review-pr was removed in v2.13.0, so `entry: legacy` and a request for "the legacy review-pr workflow" are refused. Not fo...Votes: 0GitHub stars: 3