skills.rest
TrebuchetDynamics
TrebuchetDynamicsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gormes-review-loop

Automates structured review loops by capturing failure evidence and iterating until the gate is green.

9|Updated Apr 19, 2026
Search Tags:#tdd#ci-failures#pr-review#issue-classification#review-loop#evidence-capture#planner-routing
One-click install
npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-review-loop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gormes-review-loop
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-review-loop
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-review-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when Gormes work has PR feedback, CI failures, reviewer comments, static-analysis findings, or a need to iterate until a bounded validation target is green.

Core Features & Use Cases

  • Capture the target gate and exact failing evidence (review comments, GitHub checks, CI annotations, test outputs) to drive precise remediation.
  • Classify each issue as bug, test drift, docs drift, style, blocker, or backlog work, enabling focused triage.
  • Route broad feedback to gormes-planner when it must become canonical backlog work; otherwise use gormes-tdd-slice for focused, incremental fixes.
  • Re-run the target gate after edits and repeat until green, documenting blockers if scope expands.

Quick Start

Initiate a targeted review loop by capturing the exact failure evidence and iterating until the gate is green.

Frequently Asked Questions about gormes-review-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PR review feedback and CI failures remediation?▼

Automate structured review loops by capturing exact failure evidence from PR comments or CI checks, classifying the issues, and iterating fixes until the validation gate is green.

What is the best way to iterate on CI failures until tests pass?▼

The best way to resolve CI failures is to capture the exact failing evidence, route focused fixes incrementally, and re-run the target gate validation repeatedly until it turns green.

How do you classify GitHub workflow issues during a code review?▼

Classify GitHub workflow issues by categorizing each failure evidence as a bug, test drift, docs drift, style issue, blocker, or backlog work to enable focused triage and remediation.

When should I route reviewer comments to a planner instead of fixing them directly?▼

Route broad reviewer comments to a planner when the feedback must become canonical backlog work, otherwise apply focused incremental fixes directly to pass the validation gate.

Can I use static-analysis findings for iterative test validation in CI?▼

Yes, you can capture static-analysis findings as exact failure evidence, classify the issues, and iterate targeted fixes until the bounded validation target gate is green.

What should I do if scope expands during a CI failure review loop?▼

If scope expands during a CI failure review loop, you should document the encountered blockers and route the broad feedback to a planner to establish it as canonical backlog work.

Related Skills

Explore More Software Engineering Skills→
SoundBlasterSoundBlaster
20

gh-pr-results-review

Identify failing GitHub PR checks and extract evidence lines from Actions logs.

Community
Intermediate
matteocervellimatteocervelli
25

pr-merge

Validate CI/CD checks, reviews, conflicts, then merge GitHub PRs via squash, merge, or rebase.

Community
Basic
aaronsilinskasaaronsilinskas

as-work-on-issue

Automate GitHub issue handling from fetch to pull request creation.

Community
Advanced
takaokanbetakaokanbe

address-pr-review

Orchestrate parallel PR review workflows with finding triage, automated fixes, and CI monitoring.

Community
Advanced