skills.rest
julieclarkson
julieclarksonCOMMUNITY
Explore all skills by this author →
Website𝕏@julieishumanGitHub

capture-reflection

Append structured reflection events to a project's .case-study/events.json.

Updated Aug 27, 2026
Search Tags:#git#documentation#events#reflection#capture#case-study#developer-notes
One-click install
npx skills add https://github.com/julieclarkson/case-study-maker --skill capture-reflection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capture-reflection
Source: https://github.com/julieclarkson/case-study-maker/tree/main/skills/capture-reflection
Command: npx skills add https://github.com/julieclarkson/case-study-maker --skill capture-reflection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture developer reflections at meaningful moments and persist them as structured events in a project's case study, so decisions, tradeoffs, and learnings are recorded without manual bookkeeping.

Core Features & Use Cases

  • Help developers articulate answers to focused prompts (constraints, tradeoffs, risks, security, iteration) immediately after commits or decisions.
  • Reference the latest commit hash and append a concise JSON event to .case-study/events.json, creating the file if it does not exist.
  • Use Case: After merging a PR that changes the authentication flow, invoke capture-reflection to record the tradeoffs and security considerations that informed the change.

Quick Start

Ask the plugin to capture a reflection by saying 'capture reflection' or 'add to case study' after a relevant commit.

Frequently Asked Questions about capture-reflection

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

FAQPage Schema
How do I capture developer reflections and save them to a case study timeline?▼

To capture developer reflections, invoke the plugin after a commit or design decision to append a structured JSON event with an 8-hex UUID, ISO-8601 timestamp, and related commit hash to .case-study/events.json.

What is the best way to document architecture decisions and tradeoffs automatically in git?▼

Documenting architecture decisions in git is done by capturing focused prompts on constraints, tradeoffs, and security immediately after a commit, then confirming the content before writing it as a concise JSON event to your case study timeline.

Does capture-reflection require any dependencies or external components to write events?▼

Capture-reflection requires no dependencies or external components; it creates and updates the .case-study/events.json file directly within your project repository without needing additional packages.

Can I add developer notes to an existing case study file after merging a PR?▼

Yes, you can add developer notes after merging a PR by invoking the plugin, which appends a concise reflection event to your existing .case-study/events.json file or creates it if it does not exist.

When should I record developer notes and tradeoffs in a project case study?▼

You should record developer notes in a project case study when developers commit, merge, make architecture or design decisions, or when an automated rule suggests capturing a meaningful moment during development.

What format does the plugin use to store reflection events in the case study?▼

The plugin stores reflection events in .case-study/events.json using a concise JSON structure that includes an 8-hex UUID, an ISO-8601 timestamp, and the related git commit hash.

Related Skills

Explore More Software Engineering Skills→
raineraine
2.1k

open-pr

Draft PR descriptions from conversation context and open browser-based PR creation.

Community
Advanced
vneseyoungstervneseyoungster
27

figma-analyzer

Extract design assets, metadata, and tokens from Figma files.

Community
Advanced
juanca202juanca202

speckit-git-commit

Automate Git commits after Spec Kit command events.

Community
Basic
hulusi-tunchulusi-tunc
3

document

Document feature accessibility decisions, tradeoffs, and WCAG compliance mappings.

Community
Advanced