implement-review-fix-workflow

Automate implement-review-fix cycles with dry-run validation and artifact tracking.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/errard70101/social-science-research-skills --skill implement-review-fix-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-review-fix-workflow
Source: https://github.com/errard70101/social-science-research-skills/tree/main/skills/implement-review-fix-workflow
Command: npx skills add https://github.com/errard70101/social-science-research-skills --skill implement-review-fix-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured, repeatable workflow to develop, implement, and review repository skills, prompts, references, and tests via a safe, dry-run-first cycle.

Core Features & Use Cases

  • Orchestrates a two-party implementer-reviewer loop with prompts and reports to drive iterative skill development.
  • Stores workflow artifacts under .skill-workflow-runs for traceability and reproducibility.
  • Supports a dry-run mode and configurable maximum fix cycles to validate changes before applying them.

Quick Start

Start by running the dry-run workflow to simulate implementer and reviewer prompts without touching files.

Frequently Asked Questions about implement-review-fix-workflow

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

FAQPage Schema
How do I automate an iterative code review and fix workflow for skill development?

A dry-run workflow simulates implementer and reviewer prompts without touching files. It uses snapshot-based checks and workflow guardrails to validate repository skills and prompts safely before applying changes.

How do I validate prompts and repository skills without altering existing files?

The workflow supports configurable maximum fix cycles to control iterative development. It enforces workflow guardrails and tracks artifacts to ensure reproducible, non-destructive validation of repository skills and tests.

Can I use a two-person implementer and reviewer loop to iteratively develop tests?

Workflow artifacts are stored under the .skill-workflow-runs directory. This ensures traceability and reproducibility for the implementer-reviewer loop, prompts, and reports generated during skill development.

What is the best way to structure a non-destructive implement-review-fix cycle?

Workflow artifacts are stored under the .skill-workflow-runs directory. This ensures traceability and reproducibility for the implementer-reviewer loop, prompts, and reports generated during skill development.

Does the automated code review workflow store reports and artifacts for traceability?

Workflow artifacts are stored under the .skill-workflow-runs directory. This ensures traceability and reproducibility for the implementer-reviewer loop, prompts, and reports generated during skill development.

Why do I need snapshot-based checks during prompt and skill development?

Workflow artifacts are stored under the .skill-workflow-runs directory. This ensures traceability and reproducibility for the implementer-reviewer loop, prompts, and reports generated during skill development.