reflect

Audit recent code changes for correctness, conventions, architecture, and testing.

159|41|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill reflect-atelier-fashion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/atelier-fashion/adlc-toolkit/tree/main/reflect
Command: npx skills add https://github.com/atelier-fashion/adlc-toolkit --skill reflect-atelier-fashion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-implementation self-review helps you catch issues before /review, reducing rework and downstream defects.

Core Features & Use Cases

  • Independent assessment of recent changes for correctness, conventions, architecture, tests, and completeness.
  • Enables quick identification of gaps in code quality and adherence to project standards.
  • Use case: after a feature is implemented, run a personal audit to surface issues prior to peer review.

Quick Start

Run a quick, single-pass reflection on your latest changes to surface issues before /review.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I perform a post-implementation self-review to catch code issues before peer review?

Post-implementation self-review automates an audit of recent changes for correctness, conventions, architecture, tests, and completeness to catch issues before peer review. It launches a reflector agent to run checks and report issues, clean areas, and questions.

What is the best way to audit recent code branches for adherence to project conventions?

Auditing recent code branches for project conventions is handled by an automated reflector agent that runs canonical checks on your commits. It surfaces gaps in code quality and adherence to project standards before formal review.

Can I run an automated code quality check on my latest commits without triggering a full review?

You can run a quick, single-pass reflection on your latest commits to surface issues independently. This automated assessment checks correctness, architecture, tests, and conventions without triggering a full formal review.

Does self-reviewing code changes before /review reduce downstream defects?

Self-reviewing code changes before /review reduces downstream defects and rework. The reflection process identifies gaps in completeness and quality early, ensuring issues are caught and resolved independently before peer review.

What aspects of recently implemented features are checked during an automated self-review?

An automated self-review checks recently implemented features for correctness, conventions, architecture, testing, and completeness. It evaluates these dimensions to report clean areas, surface issues, and ask clarifying questions.

When do I need to run an automated reflection on my code changes?

You need to run an automated reflection on your code changes after a feature is implemented but before submitting for peer review. This timing allows you to surface and fix issues independently, reducing downstream rework.