mcpbeat

Observe Before Editing

vibeeval/observe-before-editing

Observe Before Editing

275 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
521
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vibeeval/vibecosystem --skill observe-before-editing

The instruction itself

5 sections, as written by the author

Observe Before Editing

Before editing code to fix a bug, confirm what the system *actually produced*.

Pattern

Outputs don't lie. Code might. Check outputs first.

DO

  • Check if expected directories exist: ls -la .claude/cache/
  • Check if expected files were created: ls -la .claude/cache/learnings/
  • Check logs for errors: tail .claude/cache/*.log
  • Run the failing command manually to see actual error
  • Only then edit code

DON'T

  • Assume "hook didn't run" without checking outputs
  • Edit code based on what you *think* should happen
  • Confuse global vs project paths (check both: .claude/ and ~/.claude/)

Source Sessions

  • a541f08a: Token limit error was invisible until manual run revealed it
  • 6a9f2d7a: Looked in wrong cache path (~/.claude/ vs .claude/), assumed hook failure
  • a8bd5cea: Confirmed hook worked by finding output files in project cache
  • 1c21e6c8: Verified Artifact Index indexing by checking DB file exists

How to use it

Copy the folder

Take vibeeval/observe-before-editing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.