dev: add /bug-hunt skill for instrumentation e2e testing

[sohankshirsagar]

Adds a /bug-hunt Claude Code skill that automates finding gaps in instrumentation code by writing and running e2e tests through the DISABLED → RECORD → REPLAY cycle.

Usage: /bug-hunt <library> [focus on area - optional]

[tusk-dev]

No tests generated

Tip

New to Tusk Unit Tests? Learn more here.

No symbols were selected for unit test generation because the code changes are limited to documentation/configuration updates, .gitignore modifications, and simple command string replacements in base_runner.py. These updates do not introduce new logic, algorithms, or behavior, and testing would only verify string literals, which provides negligible value for unit testing.

View check history

Commit	Status	Output	Created (UTC)
f5d2b1e	No tests generated	Output	Mar 24, 2026 10:57PM
adeac9a	No tests generated	Output	Mar 24, 2026 11:15PM
838ae93	No tests generated	Output	Mar 24, 2026 11:23PM
1e3f40d	No tests generated	Output	Mar 24, 2026 11:30PM

[cubic-dev-ai]

3 issues found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name=".claude/commands/bug-hunt.md">

<violation number="1" location=".claude/commands/bug-hunt.md:221">
P1: Use the parsed library variable (not full `$ARGUMENTS`) when changing into the e2e directory; optional focus text can break the path.</violation>

<violation number="2" location=".claude/commands/bug-hunt.md:429">
P1: `git add` should target the parsed library directory, not `$ARGUMENTS`, to avoid invalid paths when focus context is provided.</violation>

<violation number="3" location=".claude/commands/bug-hunt.md:436">
P2: Push should use the same library-based branch name format as branch creation; using `$ARGUMENTS` can produce an invalid or mismatched branch.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cubic-dev-ai]

1 issue found across 5 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="drift/instrumentation/e2e_common/base_runner.py">

<violation number="1" location="drift/instrumentation/e2e_common/base_runner.py:300">
P3: Debug output now says `tusk drift run`, but the code still executes `tusk run`. This mismatch makes failure logs misleading during e2e debugging.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}