Agent skill

Vibe Reflect And Compound

by ash1794 in ash1794/vibe-engineering

Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent…

MITAuto-check passedDevelopment

Install Vibe Reflect And Compound

skills CLI
$ npx skills add ash1794/vibe-engineering --skill vibe-reflect-and-compound -a claude-code

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

GitHub CLI
$ gh skill install ash1794/vibe-engineering vibe-reflect-and-compound --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/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-reflect-and-compound .claude/skills/vibe-reflect-and-compound && 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
vibe-reflect-and-compound
GitHub stars
163
Token cost
~864 tokens
SKILL.md length
370 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
MIT

At a glance

Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent…

  • Works in 3 steps: Learning → Bug → Pattern (only at the third occurrence)
  • Tasks that involve Root cause analysis
  • SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Where to Save and Entry Types, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Vibe Reflect And Compound is an agent skill from ash1794/vibe-engineering. Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file. Use after feedback, a non-trivial bug fix, a failed attempt, or the third repetition of a pattern.

Its SKILL.md is about 860 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, covering Root cause analysis, Debugging and Agent memory. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.

When your agent uses it

  • Tasks that involve Root cause analysis
  • Tasks that involve Debugging
  • Tasks that involve Agent memory

Example prompts

  • “Use the vibe-reflect-and-compound skill to capture reusable knowledge after work is done — learnings from feedback or failures, resolved bugs…”
  • “/vibe-reflect-and-compound”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Learning
  2. Bug
  3. Pattern (only at the third occurrence)

What it can do on your machine

Read from SKILL.md and the folder at commit 8f1d71b. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    No URLs in SKILL.md.

    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

Vibe Reflect And Compound loads about 864 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 370 words of instructions outside code blocks.

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

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 ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 370 words, ~864 tokens.

Download SKILL.mdSave it as .claude/skills/vibe-reflect-and-compound/SKILL.md (or your agent's skills folder).
name
vibe-reflect-and-compound
description
Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file. Use after feedback, a non-trivial bug fix, a failed attempt, or the third repetition of a pattern.
user-invocable
true

vibe-reflect-and-compound

Every problem solved should leave something behind that makes the next one cheaper. This skill records it in the one place the agent will actually read next session.

When to Use This Skill

  • After receiving feedback on your work (positive or negative)
  • After resolving a non-trivial bug: it took more than ~10 minutes, was hard to reproduce, or had a surprising root cause
  • After a failed attempt or an approach that had to be abandoned
  • When you implement the same code pattern for the third time
  • At the end of a complex task

When NOT to Use This Skill

  • After trivial tasks (typos, renames, obvious fixes)
  • When nothing new was learned
  • During active implementation (reflect after, not during)
  • For architectural decisions (use vibe-decision-journal, which keeps ADRs in the repo)

Where to Save

Write to the memory file the current agent loads automatically. A separate LEARNINGS.md that nothing loads is write-only.

AgentLoaded automatically
Claude CodeCLAUDE.md (project) or auto-memory, if enabled
OpenAI CodexAGENTS.md
Gemini CLIGEMINI.md, or the built-in memory tool
Shared across toolsAGENTS.md, imported or referenced from the others

Keep the always-loaded file short. Put long entries in docs/learnings/ (bugs, patterns, learnings) and add a one-line pointer to them in the memory file.

Entry Types

1. Learning
- **[Pattern name]**: [actionable rule]. Applies when: [context]. Evidence: [what happened].

Be actionable and specific. Not "be careful with concurrency" but "run the race detector before committing code that touches sessionCache."

Show full SKILL.md (139 more words)Show less
2. Bug
### [Category]: [short description] ([date])
Symptom: [what was observed]
Root cause: [the actual problem]
Why hard to find: [what misled the investigation]
Fix: [what changed] — Prevention: [test, lint rule, or guard added]
Files: [paths]

Categories: Concurrency, State, Validation, Integration, Environment, UI.

3. Pattern (only at the third occurrence)
### [Pattern name] — [category]
When to use: [situation]
Canonical example: [file:line]
Anti-pattern: [the common mistake]

Point to the canonical implementation in the codebase instead of copying code into the memory file.

Steps

  1. Gather — What happened? What was expected vs. what actually happened? What was the root cause?
  2. Extract — What would have caught this earlier? Is it a recurring theme? Search existing entries first, and update or merge instead of duplicating.
  3. Write the entry in the right format.
  4. Prune — Keep at most ~30 active learnings in the always-loaded file. Merge similar ones, and move stale ones to docs/learnings/archive.md.
  5. Confirm — Show the entry to the user before saving if it changes shared project instructions.

Output Format

Reflection: [context]

Trigger: [what prompted this]

Entries:

  1. [Type] [Name]: [one-line summary]

Saved to: [file path(s)] Active learnings: X/30

© ash1794, 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 plugins/vibe-engineering/skills/vibe-reflect-and-compound of ash1794/vibe-engineering.

Open the folder on GitHubat commit 8f1d71b

Compare with similar skills

Vibe Reflect And Compound 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.

Vibe Reflect And Compound compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vibe Reflect And Compound this skillash1794/vibe-engineering163—~864Automated safety check: PassMIT
Octocode Code Researchbgauryy/octocode949—~1.5kAutomated safety check: PassMIT
Muse Code Product Doctorasgeirtj/system_prompts_leaks69k—~3.5kAutomated safety check: PassCC0-1.0
Root Cause Investigationgarrytan/gstack136k—~13kAutomated safety check: NotesMIT
Evidence-Driven TraceYeachan-Heo/oh-my-claudecode40k—~2.6kAutomated safety check: PassMIT
Targeted Emergency Bug FixVeryGoodOpenSource/vgv-wingspan109—~1.9kAutomated safety check: PassMIT

Similar skills

  • Octocode Code Research

    bgauryy/octocode

    Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.

    949 GitHub stars~1.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Muse Code Product Doctor

    asgeirtj/system_prompts_leaks

    Diagnoses a Muse Code installation's own failures from binary and session evidence, instead of treating the report as an ordinary repository bug.

    69k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.

    136k GitHub stars~13k tokensUpdated today
    DevelopmentAuto-check: notes
  • Evidence-Driven Trace

    Yeachan-Heo/oh-my-claudecode

    Explains why something happened by generating competing hypotheses, gathering evidence in parallel, ranking explanations and proposing the next discriminating probe.

    40k GitHub stars~2.6k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Targeted Emergency Bug Fix

    VeryGoodOpenSource/vgv-wingspan

    Applies a minimal fix to an emergency bug through triage, root-cause location, a hotfix branch and a blast-radius check, with tests and review still required.

    109 GitHub stars~1.9k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • OMC Session Debugger

    Yeachan-Heo/oh-my-claudecode

    Diagnoses a broken oh-my-claudecode session or repository state from logs, traces, state and a narrow reproduction, then names the smallest next fix.

    40k GitHub stars~361 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from ash1794/vibe-engineering

All 33 skills in this repo
  • Vibe Concurrent Test Safety

    ash1794/vibe-engineering

    Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.

    163 GitHub stars~665 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Fuzz Parser Inputs

    ash1794/vibe-engineering

    Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).

    163 GitHub stars~722 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Golden File Testing

    ash1794/vibe-engineering

    Implements snapshot/golden file tests with temporal normalization so tests don't break daily.

    163 GitHub stars~669 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Parallel Task Decomposition

    ash1794/vibe-engineering

    Analyzes large tasks for independent subtasks that can be safely parallelized.

    163 GitHub stars~717 tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Slop Filter

    ash1794/vibe-engineering

    Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).

    163 GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed
  • Vibe Spec Sync

    ash1794/vibe-engineering

    Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.

    163 GitHub stars~2.2k tokensUpdated 3 days ago
    Auto-check passed

Questions about Vibe Reflect And Compound

What does Vibe Reflect And Compound do?

Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent…. Vibe Reflect And Compound is an agent skill from ash1794/vibe-engineering. Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file.

When should I use Vibe Reflect And Compound?

Vibe Reflect And Compound fits situations like: tasks that involve Root cause analysis; tasks that involve Debugging; tasks that involve Agent memory.

How do I install Vibe Reflect And Compound in Claude Code?

Run `npx skills add ash1794/vibe-engineering --skill vibe-reflect-and-compound -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-reflect-and-compound in ash1794/vibe-engineering) into .claude/skills/vibe-reflect-and-compound in your project. Claude Code loads it when a task matches its description.

How do I install Vibe Reflect And Compound in Codex?

Run `npx skills add ash1794/vibe-engineering --skill vibe-reflect-and-compound -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-reflect-and-compound in ash1794/vibe-engineering) into .agents/skills/vibe-reflect-and-compound in your project. Codex loads it when a task matches its description.

Can I use Vibe Reflect And Compound 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 ash1794/vibe-engineering --skill vibe-reflect-and-compound -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-reflect-and-compound, .gemini/skills/vibe-reflect-and-compound, .github/skills/vibe-reflect-and-compound and .opencode/skills/vibe-reflect-and-compound in your project.

What does Vibe Reflect And Compound need to run?

SKILL.md names no scripts, command-line tools or credentials: Vibe Reflect And Compound is instructions for the agent only.

Does Vibe Reflect And Compound access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vibe Reflect And Compound 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 Vibe Reflect And Compound use?

Vibe Reflect And Compound 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 Vibe Reflect And Compound use?

About 864 tokens (SKILL.md is roughly 3.5k 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 Vibe Reflect And Compound?

Skills that share tags, products or a category with Vibe Reflect And Compound: Octocode Code Research (bgauryy/octocode, 949 stars), Muse Code Product Doctor (asgeirtj/system_prompts_leaks, 69k stars), Root Cause Investigation (garrytan/gstack, 136k stars) and Evidence-Driven Trace (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vibe Reflect And Compound?

ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.

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