reflect

Inspect git history and planning artifacts to produce a reflection document.

5|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/agentpatterns/craft --skill reflect-agentpatterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reflect
Source: https://github.com/agentpatterns/craft/tree/main/plugins/crafter/skills/reflect
Command: npx skills add https://github.com/agentpatterns/craft --skill reflect-agentpatterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

After a substantive session, teams struggle to extract learnings and plan concrete improvements. The Reflect skill automates mining git history, artifacts, and context to produce a structured improvement proposal.

Core Features & Use Cases

  • Mines git history and artifacts to surface learnings and friction points.
  • Generates concrete improvement proposals for CLAUDE.md, hooks, and templates.
  • Writes a reflection artifact to docs/plans/YYYY-MM-DD-{topic}-reflection.md.

Quick Start

Describe the session and run the Reflect workflow to produce a reflection and a set of improvement proposals.

Frequently Asked Questions about reflect

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

FAQPage Schema
How do I extract learnings from git history after a coding session?

Extract learnings from git history by running the Reflect workflow, which mines commits, planning artifacts, and context files to produce a structured reflection artifact with concrete improvement proposals.

What is the best way to generate improvement proposals from planning artifacts?

Generate improvement proposals from planning artifacts by analyzing docs/plans and key context files to surface friction points, then outputting actionable recommendations aligned with the improvement-guide taxonomy.

How do I create a post-session reflection artifact for my project?

Create a post-session reflection artifact by running the Reflect workflow after a substantive session, which writes a structured summary to docs/plans/YYYY-MM-DD-{topic}-reflection.md and records an Agent Dispatch Manifest.

Can I automate mining git history to produce recommendations for CLAUDE.md and hooks?

Yes, you can automate mining git history to produce recommendations for CLAUDE.md and hooks by running the Reflect workflow, which generates concrete improvement proposals based on session learnings and friction points.

Does the Reflect workflow require any dependencies to inspect git history and planning artifacts?

The Reflect workflow requires no external dependencies to inspect git history and planning artifacts, operating directly on your repository's commit log, docs/plans directory, and key context files.

When should I not use a post-session reflection workflow for my repository?

You should not use a post-session reflection workflow after trivial or non-substantive sessions, as the tool is designed to extract learnings and friction points from meaningful development work that produces notable git history and planning artifacts.