hello-reflect

Generates session reflections and appends lessons learned to project knowledge base documents.

702|99|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/hellowind777/helloagents --skill hello-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hello-reflect
Source: https://github.com/hellowind777/helloagents/tree/main/skills/hello-reflect
Command: npx skills add https://github.com/hellowind777/helloagents --skill hello-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After completing difficult tasks, valuable lessons learned during debugging and verification loops are often lost. This Skill captures those insights as structured reflections and persists them into the project knowledge base so future sessions can benefit.

Core Features & Use Cases

  • Triggered Reflection: Activates after tasks that required 2+ verification loops, 3+ debugging attempts, plan changes, or user corrections.
  • Incremental Knowledge Appending: Appends dated lessons to the experience sections of relevant modules/*.md files, or to context.md for project-level insights, without rewriting existing content.
  • Quality Guardrails: Enforces abstract, concise guidance (max 2 lines per lesson) instead of concrete code templates that could anchor future sessions on wrong details.
  • Use Case: After a session where a bug took four attempts to fix, run this Skill to record the root-cause pattern as a reusable lesson in the relevant module document.

Quick Start

Ask the agent to generate a session reflection and append the lessons learned to the relevant knowledge base module documents.

Frequently Asked Questions about hello-reflect

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

FAQPage Schema
How do I capture lessons learned after an AI coding session?

Run a reflection pass after task completion that extracts abstract lessons and appends them to the experience section of the relevant knowledge base module files. Each entry is dated and limited to two lines of guidance.

When should a session reflection be generated?

Generate a reflection when a task needed 2 or more verification loops, debugging took more than 3 attempts, the plan changed mid-execution, or the user corrected a wrong assumption. Routine smooth tasks do not require one.

Where are reflection lessons stored in the knowledge base?

Lessons are appended incrementally to the experience section of the relevant modules/*.md files. Project-level insights that fit no specific module go into a new experience section at the end of context.md.

Why should lessons be abstract instead of code templates?

Concrete code templates can anchor future AI sessions on incorrect details when contexts differ. Abstract guidance generalizes across situations, so each lesson is kept to at most two lines of transferable principle.

Does reflection rewrite existing knowledge base content?

No, reflection only appends new dated entries to existing experience sections. It never rewrites or deletes prior content, preserving the accumulated history of lessons.