Agent skill

Reflection

by straubt1 in straubt1/tfx

This skill should be used when the user says "reflection", "reflect on the changes", "reflect on this session", or asks to capture lessons learned from the current conversation.

MITAuto-check passedDevelopment

Install Reflection

skills CLI
$ npx skills add straubt1/tfx --skill reflection -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install straubt1/tfx reflection --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/straubt1/tfx.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/reflection .claude/skills/reflection && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
reflection
GitHub stars
110
Token cost
~793 tokens
SKILL.md length
338 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

This skill should be used when the user says "reflection", "reflect on the changes", "reflect on this session", or asks to capture lessons learned from the current conversation.

  • Works in 8 steps: Read the full conversation from top to… → Review the diffs (supplementary) — Read… → Identify lessons in these categories → …
  • Says reflection
  • SKILL.md covers Current Git State…, Process and Output Format
  • Calls git

What it does

Reflection is an agent skill from straubt1/tfx. This skill should be used when the user says "reflection", "reflect on the changes", "reflect on this session", or asks to capture lessons learned from the current conversation.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with Git. The repository describes itself as: TFx is a standalone CLI for HCP Terraform and Terraform Enterprise. The licence is MIT.

When your agent uses it

  • Says reflection
  • Reflect on the changes
  • Reflect on this session
  • Asks to capture lessons learned from the current conversation

Example prompts

  • “reflection”
  • “reflect on the changes”
  • “reflect on this session”
  • “/reflection”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Read the full conversation from top to bottom. Pay attention to
  2. Review the diffs (supplementary) — Read modified files for context on what was built and why, but do not let this overshadow lessons from…
  3. Identify lessons in these categories
  4. Read the current CLAUDE.md to avoid duplicating what's already there and to find gaps.
  5. Propose edits to CLAUDE.md — For each lesson worth keeping, suggest the specific text to add, change, or remove, and where it belongs.
  6. If no lessons are found, explicitly state: "No CLAUDE.md updates needed from this session." This confirms the session was considered.
  7. Do not apply edits automatically. Present proposals to the user and wait for approval.
  8. After applying approved edits, print a brief summary in chat of what changed.

What it can do on your machine

Read from SKILL.md and the folder at commit f7494e5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Reflection loads about 793 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 338 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~793

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from straubt1/tfx at commit f7494e5, republished under its MIT licence (© straubt1). 338 words, ~793 tokens.

Download SKILL.mdSave it as .claude/skills/reflection/SKILL.md (or your agent's skills folder).
name
reflection
description
This skill should be used when the user says "reflection", "reflect on the changes", "reflect on this session", or asks to capture lessons learned from the current conversation.
disable-model-invocation
true

Reflection

The goal is to identify lessons from this session that should be permanently captured in CLAUDE.md — so future sessions benefit without repeating the same mistakes, clarifications, or decisions.

Review the entire conversation history — every message, correction, and preference — as the primary source. Code diffs are supplementary.

Current Git State (supplementary context)

  • Branch: !git branch --show-current
  • Changes since last commit: !git diff --stat HEAD
  • Staged changes: !git diff --stat --cached

Process

  1. Read the full conversation from top to bottom. Pay attention to:

    • Questions the user had to answer that should have been obvious from CLAUDE.md
    • Corrections the user made to your approach or output
    • Preferences or constraints the user stated (even casually)
    • Things you got wrong on the first attempt and had to revise
    • Decisions made about architecture, naming, tooling, or workflow
    • Anything the user explicitly said to always/never do
  2. Review the diffs (supplementary) — Read modified files for context on what was built and why, but do not let this overshadow lessons from the conversation itself.

  3. Identify lessons in these categories:

    • Patterns & conventions — Things that worked well and should be encoded as rules
    • Gotchas & pitfalls — Things that caused confusion, required retries, or were non-obvious
    • Architecture decisions — Choices made that future sessions should know about
    • Workflow & communication preferences — How the user prefers to work, communicate, or receive output
    • Outdated/wrong memory — Anything in CLAUDE.md or MEMORY.md that turned out to be incorrect or missing
  4. Read the current CLAUDE.md to avoid duplicating what's already there and to find gaps.

  5. Propose edits to CLAUDE.md — For each lesson worth keeping, suggest the specific text to add, change, or remove, and where it belongs.

  6. If no lessons are found, explicitly state: "No CLAUDE.md updates needed from this session." This confirms the session was considered.

  7. Do not apply edits automatically. Present proposals to the user and wait for approval.

  8. After applying approved edits, print a brief summary in chat of what changed.

Output Format

When lessons are found:

## Reflection

### [Category]
**Lesson**: <what was learned>
**Proposed CLAUDE.md change**: <exact text, with target section>

---
(one block per lesson)

When no lessons are found:

## Reflection

No CLAUDE.md updates needed from this session. The following were considered but already covered or not worth persisting:
- <item> — already in CLAUDE.md / too session-specific / etc.

After applying approved changes:

## CLAUDE.md updated

- Added: "<description>" under ## Section
- Modified: "<what changed>" in ## Section
- Removed: "<what was removed>"

© straubt1, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/reflection of straubt1/tfx.

Open the folder on GitHubat commit f7494e5

Compare with similar skills

Reflection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Reflection compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Reflection this skillstraubt1/tfx110—~793Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything86k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    86k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    86k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from straubt1/tfx

  • Go Upgrade

    straubt1/tfx

    Upgrade macOS Go and all module dependencies in TFx via task go:upgrade, then verify build and tests.

    110 GitHub stars~914 tokensUpdated 1 mo ago
    Auto-check: notes
  • Release

    straubt1/tfx

    Prepare and cut TFx semver releases (CHANGELOG, validation, tagging via Taskfile).

    110 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Vhs Tape

    straubt1/tfx

    Create a VHS .tape file for recording terminal GIF/MP4/WebM demos.

    110 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • New Data Function

    straubt1/tfx

    Create a new function in the data/ package following project conventions

    110 GitHub stars~976 tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Reflection

What does Reflection do?

This skill should be used when the user says "reflection", "reflect on the changes", "reflect on this session", or asks to capture lessons learned from the current conversation. Reflection is an agent skill from straubt1/tfx. This skill should be used when the user says "reflection", "reflect on the changes", "reflect on this session", or asks to capture lessons learned from the current conversation.

When should I use Reflection?

Reflection fits situations like: says reflection; reflect on the changes; reflect on this session; asks to capture lessons learned from the current conversation.

How do I install Reflection in Claude Code?

Run `npx skills add straubt1/tfx --skill reflection -a claude-code`. Or copy the skill folder (.claude/skills/reflection in straubt1/tfx) into .claude/skills/reflection in your project. Claude Code loads it when a task matches its description.

How do I install Reflection in Codex?

Run `npx skills add straubt1/tfx --skill reflection -a codex`. Or copy the skill folder (.claude/skills/reflection in straubt1/tfx) into .agents/skills/reflection in your project. Codex loads it when a task matches its description.

Can I use Reflection in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add straubt1/tfx --skill reflection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reflection, .gemini/skills/reflection, .github/skills/reflection and .opencode/skills/reflection in your project.

What does Reflection need to run?

Going by SKILL.md and its folder, Reflection needs the command-line tools its instructions call (git).

Does Reflection access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Reflection safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Reflection use?

Reflection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Reflection use?

About 793 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Reflection?

Skills that share tags, products or a category with Reflection: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Reflection?

straubt1 (a GitHub user) maintains it in straubt1/tfx, which has 110 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on August 28, 2026.

Source: straubt1/tfx on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.