skills.rest
evanklem
evanklemCOMMUNITY
Explore all skills by this author →
GitHub

evanflow-iterate

Run quality checks and re-read diffs to polish implemented changes.

417|18|Updated Apr 27, 2026
Search Tags:#tdd#iteration#refactor#code-review#diff-review#quality-checks
One-click install
npx skills add https://github.com/evanklem/evanflow --skill evanflow-iterate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evanflow-iterate
Source: https://github.com/evanklem/evanflow/tree/main/skills/evanflow-iterate
Command: npx skills add https://github.com/evanklem/evanflow --skill evanflow-iterate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, repeatable loop for reviewing and refining code after implementing a plan, reducing defects by systematically re-reading changes, detecting dead code, and enforcing quality gates.

Core Features & Use Cases

  • Run project quality checks (typecheck, lint, tests) to ensure changes are safe
  • Re-read the diff with fresh eyes to identify dead code, naming inconsistencies, and potential scope creep
  • Apply Five Failure Modes guardrails to guard against hallucinations, scope creep, cascading errors, context loss, and tool misuse
  • Stop and report results to the user for direction on next steps

Quick Start

Provide the latest changes to evanflow-iterate and run the loop until quality gates pass and you are ready to progress.

Frequently Asked Questions about evanflow-iterate

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

FAQPage Schema
How do I run an iterative code review to polish a diff before submitting?▼

Yes, self-reviewing code changes can detect cascading errors and scope creep by re-reading diffs and running quality checks. Applying failure mode guardrails during this review prevents hallucinations, context loss, and tool misuse, ensuring changes are safe and ready for review.

What is the best way to enforce failure mode guardrails during refactoring?▼

An iterative self-review loop polishes implemented changes by running tests, typechecks, and linters. It re-reads diffs to identify dead code and scope creep, applies fixes, and stops to report changes and remaining risks for user direction.

How do I automatically run quality checks and re-read diffs after implementing a plan?▼

No special dependencies are required to run iterative code review loops. The process relies on your existing project quality checks like typecheck, lint, and tests to validate changes, re-read diffs, and enforce guardrails against scope creep and hallucinations.

When should I use an iterative self-review loop for code quality checks?▼

An iterative self-review loop complements TDD workflows by validating implemented changes after tests pass. It re-reads diffs with fresh eyes, applies failure mode guardrails against context loss and tool misuse, and ensures the final code is clean and ready for review.

Related Skills

Explore More Software Engineering Skills→
Hyeonjun0527Hyeonjun0527
1

validate

Run lint, format, typecheck, and build verification pipelines on code changes.

Community
Intermediate
Doyajin174Doyajin174
1

report-writing

Generate structured post-work reports with change logs and validation results.

Community
Intermediate
superfhpsuperfhp

requesting-code-review

Automate pre-commit code review by scanning git diffs for security vulnerabilities and quality issues.

Community
Advanced
acidsoundacidsound

code-quality

Inspect web audio application code for dead code, magic numbers, and type safety issues.

Community
Intermediate