What is vibe-debugging-journal?

Un journal persistant des problèmes logiciels résolus, classés par catégorie. Il note le symptôme, la cause réelle, la difficulté, la correction et les moyens d’éviter le retour du problème.

Il sert à documenter les bugs non triviaux, repérer des problèmes qui se répètent et conserver les solutions trouvées.

Il évite de chercher à nouveau la cause de bugs complexes ou difficiles à reproduire.

vibe-debugging-journal — Skill by ash1794

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/ash1794/vibe-engineering/debugging-journal

Any agent

npx skills add ash1794/vibe-engineering --skill debugging-journal

Clone the repo

git clone --depth 1 https://github.com/ash1794/vibe-engineering

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 418 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00033	$0.00418
Opus 5	$0.00016	$0.00209
Sonnet 5	$0.00007	$0.00084
Haiku 4.5	$0.00003	$0.00042

Measured 2d ago against content hash 01cc7039f08a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vibe-debugging-journal scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

vibe-debugging-journal — 100% identical, 0 lines differ

plugins/vibe-engineering/skills/debugging-journal/SKILL.md · 56 lines

What it actually says

vibe-debugging-journal

Bugs come in patterns. Recording them prevents re-investigation.

When to Use This Skill

After resolving a non-trivial bug (took >10 minutes to find)
After finding a bug that was hard to reproduce
After debugging something where the root cause was surprising
When you notice a bug pattern repeating

When NOT to Use This Skill

Trivial bugs (typos, missing imports)
Bugs with immediately obvious causes
Build/configuration issues (not really bugs)

Steps

Categorize the bug:
- Concurrency (race conditions, deadlocks, ordering)
- State Management (stale state, missing updates, cache invalidation)
- Type/Validation (type errors, missing validation, edge cases)
- Integration (API mismatch, version incompatibility, protocol errors)
- Environment (platform-specific, config, deployment)
- UI/Rendering (layout, hooks, lifecycle)
Record in structured format:

### [Category]: [Short description]
**Date**: [date]
**Symptom**: [What was observed]
**Root Cause**: [The actual problem]
**Why Hard to Find**: [What made debugging difficult]
**Fix**: [What was changed]
**Prevention**: [How to prevent recurrence]
**Files**: [affected files]

Save to persistent storage:
- Project: docs/debugging-journal.md or DEBUGGING.md
- Memory: Claude auto-memory or MCP
Cross-reference — If this relates to an existing journal entry, link them

Output Format

Present the entry for user confirmation, then save. Keep entries concise (5-10 lines each).

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 56 lines · 33 tokens per session scan A 01cc7039f08a

Subscribe to this mod's changes

vibe-debugging-journal is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 418 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Debugging claude-code claude-code-plugin developer-tools skills vibe-coding

vibe-debugging-journal

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

vibe-debugging-journal

When to Use This Skill

When NOT to Use This Skill

Steps

Output Format

What this file has done since we first saw it

Other skills, from other repositories

pptgen-drawio

create-skill

wechat-article-writer

project-docs

drawio-diagram

skill-prompt-convert