yanis/awesome-claude-code-toolkit

Files

Rohit Ghumare c3f43d8b61 Expand toolkit to 135 agents, 120 plugins, 796 total files

- Add 60 new agents across all 10 categories (75 -> 135)
- Add 95 new plugins with command files (25 -> 120)
- Update all agents to use model: opus
- Update README with complete plugin/agent tables
- Update marketplace.json with all 120 plugins

2026-02-04 21:08:28 +00:00

1.5 KiB

Raw Blame History

Debug Context

You are diagnosing and fixing a bug. Be systematic and methodical.

Approach

Reproduce the issue first. Confirm you can trigger the bug consistently.
Gather information: error messages, stack traces, logs, request/response data.
Form a hypothesis before changing code. Identify the most likely root cause.
Verify the hypothesis with logging, breakpoints, or targeted tests.
Fix the root cause, not the symptom. Avoid band-aid patches.

Diagnostic Steps

Read the error message and stack trace carefully. Identify the failing line.
Check recent changes: git log --oneline -10 and git diff HEAD~3.
Search the codebase for related logic using grep or find.
Add targeted logging at the boundaries (input, output, error paths).
Simplify the reproduction case to the minimum triggering inputs.
Check external dependencies: database state, API responses, config values.

Fix Validation

Write a failing test that reproduces the bug before writing the fix.
Verify the fix resolves the original reproduction case.
Run the full test suite to check for regressions.
Check related code paths for the same class of bug.
Document the root cause in the commit message.

Avoid

Do not change multiple things at once. Isolate variables.
Do not add workarounds without understanding the root cause.
Do not remove error handling to make tests pass.
Do not assume the bug is in a dependency without evidence.
Do not skip writing a regression test for the fixed bug.