Debugging

Skill furkangonel/cowrangler/bundled_skills/debugging

Autonomous terminal AI agent for workflows and feasible project procedures. Co-Worker Co-Wrangler 🐙

Install

npx -y skills add furkangonel/cowrangler --skill debugging

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Systematic bug investigation process — reproduce, isolate, root cause, fix, verify

SKILL.md

3.2 KB, as published. Nobody here has run it

Debugging SOP

The Scientific Method for Bugs

Step 1 — Understand the Symptom

Read the error message / stack trace carefully (every line)
Identify: What was expected? What actually happened?
Note: When does it occur? Always, or only sometimes?
Check: Is this a regression? When did it last work?

Step 2 — Reproduce the Bug

# Can you reproduce it reliably?
# If not, it may be:
# - Race condition (timing-dependent)
# - Environment-specific (env vars, OS, versions)
# - Data-dependent (specific inputs trigger it)

Reduce to the minimal reproduction case
Confirm the reproduction before investigating
Check if it reproduces in a fresh environment

Step 3 — Read the Code

Locate the exact file and function from the stack trace
Trace the execution path from input → failure point
Look at what changed recently: git log --since="3 days ago" -- <file>

Step 4 — Form a Hypothesis

State your hypothesis explicitly:

"I think the bug is caused by X because Y"

Then check what evidence would confirm or disprove it.

Step 5 — Verify the Hypothesis

Add targeted logging to confirm:

console.log("[DEBUG]", { variableName, type: typeof variableName });

Or use the debugger:

node --inspect-brk dist/main.js  # Attach Chrome DevTools

Step 6 — Fix

Make the minimal change that fixes the root cause
Do NOT fix symptoms — fix root causes
Do NOT refactor while fixing (separate concerns)

Step 7 — Verify the Fix

# Run existing tests
npm test

# Confirm the original reproduction no longer fails
# Add a regression test to prevent recurrence

Common Bug Patterns

Async/Await Issues

// WRONG — Promise not awaited
const data = fetchData();  // returns Promise, not data
console.log(data.name);    // undefined!

// CORRECT
const data = await fetchData();

Off-by-One

Array indices: arr[arr.length] is undefined, arr[arr.length - 1] is last
Loop boundaries: < length vs <= length

Mutation vs Copy

// WRONG — mutates original
const sorted = arr.sort();

// CORRECT — copy first
const sorted = [...arr].sort();

Environment Variables

// Always validate env vars at startup
if (!process.env.DATABASE_URL) {
  throw new Error("DATABASE_URL is required");
}

Agent Instructions

Always read the error message before looking at code
Use git_log to find recent changes that might be related
Use search_in_files to find all usages of the problematic function
Use execute_bash to run tests and confirm reproduction
Explain your reasoning at each step — debugging is a communication exercise
After fixing, always run the test suite and check for regressions

Why/Failure Modes

[TODO: Explain the reasoning behind this skill's approach and common failure modes to avoid.]

Standalone vs Supercharged

[TODO: Describe how this skill works on its own vs when combined with other tools/context.]

Cross-References

[TODO: Link to other relevant skills or documentation.]