vibe-reflect-and-compound
From the author
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.
Install
npx skills add ash1794/vibe-engineering --skill vibe-reflect-and-compound -a claude-code
Installs to .claude/skills/vibe-reflect-and-compound/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 84
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- vibeOvid/paadUse when making a small, quick change — a bug fix, typo, minor feature, tweak, or anything the user calls "vibe coding" — that looks like 1-3 files in the same moduleEngineering★ 142
- learnpedrohcgs/claude-code-my-workflowExtract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.Productivity★ 1.7K
- learn-rulerohitg00/pro-workflowCapture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for future sessions. Use after mistakes or when the user says "remember this", "don't forget", "note this", or "learn from this".Productivity★ 2.9K
- phx-compoundoliver-kriska/claude-elixir-phoenixCapture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful…Other★ 570
- issuespedrohcgs/claude-code-my-workflowKeeps a project's to-do list and memory in GitHub issues — files each finding (from a review, an audit, or the user) as its own issue without duplicates, lists the open issues that bear on the current work, and closes an issue with a comment recording what was wrong, what was tried, what worked, and how it was fixed. Use when review findings or a list of problems should become tracked work (a paper's misleading claims, a codebase's bugs, improvements for later), when starting or resuming work and deciding what to do next, or when a fix has landed and its issue should be closed with a record. Needs the GitHub CLI; warns before posting to a public repository.Science★ 1.7K
- reflectborghei/Claude-SkillsTurn reflection into decisions by scoring predictions against outcomes and tracking whether commitments held. Use when running a quarterly review, scoring forecast calibration, or reflection keeps producing notes instead of change.Engineering★ 971
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in