Add Claude Code plugin marketplace support

.claude-plugin/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "bug-hunt",
+  "owner": {
+    "name": "danpeg"
+  },
+  "description": "Adversarial bug hunting skill for Claude Code",
+  "plugins": [
+    {
+      "name": "bug-hunt",
+      "source": {
+        "source": "github",
+        "repo": "danpeg/bug-hunt"
+      },
+      "description": "Adversarial bug finding using 3 isolated agents (Hunter, Skeptic, Referee) to find and verify real bugs with high fidelity.",
+      "homepage": "https://github.com/danpeg/bug-hunt",
+      "license": "MIT",
+      "keywords": ["bug-hunting", "code-review", "adversarial", "agents"]
+    }
+  ]
+}

.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "bug-hunt",
+  "description": "Adversarial bug finding using 3 isolated agents (Hunter, Skeptic, Referee) to find and verify real bugs with high fidelity.",
+  "version": "1.0.0",
+  "author": {
+    "name": "danpeg"
+  }
+}

README.md

@@ -16,11 +16,28 @@ Each agent runs in a **completely isolated context** — they can't see each oth
 
 ## Install
 
+### Plugin marketplace (recommended)
+
+```
+/plugin marketplace add danpeg/bug-hunt
+/plugin install bug-hunt@bug-hunt
+```
+
+Skill is namespaced as `/bug-hunt:bug-hunt`. Managed automatically — updates via `/plugin marketplace update bug-hunt`.
+
+### skills.sh
+
+```bash
+npx skills add danpeg/bug-hunt
+```
+
+### Standalone (git clone)
+
 ```bash
 git clone https://github.com/danpeg/bug-hunt.git ~/.claude/skills/bug-hunt
 ```
 
-Claude Code auto-discovers skills in `~/.claude/skills/`.
+Claude Code auto-discovers skills in `~/.claude/skills/`. Skill available as `/bug-hunt`.
 
 ## Usage
 
@@ -36,12 +53,24 @@ Claude Code auto-discovers skills in `~/.claude/skills/`.
 
 ## Update
 
+Plugin marketplace:
+```
+/plugin marketplace update bug-hunt
+```
+
+Standalone:
 ```bash
 cd ~/.claude/skills/bug-hunt && git pull
 ```
 
 ## Uninstall
 
+Plugin marketplace:
+```
+/plugin uninstall bug-hunt@bug-hunt
+```
+
+Standalone:
 ```bash
 rm -rf ~/.claude/skills/bug-hunt
 ```

SKILL.md

@@ -45,9 +45,9 @@ Follow the rules in the **Target** section above to determine the scan target. I
 ### Step 2: Read the prompt files
 
 Read these files using the skill directory variable:
-- ${CLAUDE_SKILL_DIR}/prompts/hunter.md
-- ${CLAUDE_SKILL_DIR}/prompts/skeptic.md
-- ${CLAUDE_SKILL_DIR}/prompts/referee.md
+- ${CLAUDE_SKILL_DIR}/skills/bug-hunt/prompts/hunter.md
+- ${CLAUDE_SKILL_DIR}/skills/bug-hunt/prompts/skeptic.md
+- ${CLAUDE_SKILL_DIR}/skills/bug-hunt/prompts/referee.md
 
 ### Step 3: Run the Hunter Agent
 

skills/bug-hunt/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: bug-hunt
+description: "Run adversarial bug hunting on your codebase. Uses 3 isolated agents (Hunter, Skeptic, Referee) to find and verify real bugs with high fidelity. Invoke with /bug-hunt, /bug-hunt [path], or /bug-hunt -b <branch> [--base <base>]."
+argument-hint: "[path | -b <branch> [--base <base-branch>]]"
+disable-model-invocation: true
+---
+
+# Bug Hunt - Adversarial Bug Finding
+
+Run a 3-agent adversarial bug hunt on your codebase. Each agent runs in isolation.
+
+## Usage
+
+```
+/bug-hunt              # Scan entire project
+/bug-hunt src/         # Scan specific directory
+/bug-hunt lib/auth.ts  # Scan specific file
+/bug-hunt -b feature-xyz              # Scan files changed in feature-xyz vs main
+/bug-hunt -b feature-xyz --base dev   # Scan files changed in feature-xyz vs dev
+```
+
+## Target
+
+The raw arguments are: $ARGUMENTS
+
+**Parse the arguments as follows:**
+
+1. If arguments contain `-b <branch>`: this is a **branch diff mode**.
+   - Extract the branch name after `-b`.
+   - If `--base <base-branch>` is also present, use that as the base branch. Otherwise default to `main`.
+   - Run `git diff --name-only <base>...<branch>` using the Bash tool to get the list of changed files.
+   - If the command fails (e.g. branch not found), report the error to the user and stop.
+   - If no files changed, tell the user there are no changes to scan and stop.
+   - The scan target is the list of changed files (scan their full contents, not just the diff).
+2. If arguments do NOT contain `-b`: treat the entire argument string as a **path target** (file or directory). If empty, scan the current working directory.
+
+## Execution Steps
+
+You MUST follow these steps in exact order. Each agent runs as a separate subagent via the Agent tool to ensure context isolation.
+
+### Step 1: Parse arguments and resolve target
+
+Follow the rules in the **Target** section above to determine the scan target. If in branch diff mode, run the git diff command now and collect the file list.
+
+### Step 2: Read the prompt files
+
+Read these files using the skill directory variable:
+- ${CLAUDE_SKILL_DIR}/prompts/hunter.md
+- ${CLAUDE_SKILL_DIR}/prompts/skeptic.md
+- ${CLAUDE_SKILL_DIR}/prompts/referee.md
+
+### Step 3: Run the Hunter Agent
+
+Launch a general-purpose subagent with the hunter prompt. Include the scan target in the agent's task. If in branch diff mode, pass the explicit file list so the Hunter only scans those files (full contents). The Hunter must use tools (Read, Glob, Grep) to examine the actual code.
+
+Wait for the Hunter to complete and capture its full output.
+
+### Step 3b: Check for findings
+
+If the Hunter reported TOTAL FINDINGS: 0, skip Steps 4-5 and go directly to Step 6 with a clean report. No need to run Skeptic and Referee on zero findings.
+
+### Step 4: Run the Skeptic Agent
+
+Launch a NEW general-purpose subagent with the skeptic prompt. Inject the Hunter's structured bug list (BUG-IDs, files, lines, claims, evidence, severity, points). Do NOT include any narrative or methodology text outside the structured findings.
+
+The Skeptic must independently read the code to verify each claim.
+
+Wait for the Skeptic to complete and capture its full output.
+
+### Step 5: Run the Referee Agent
+
+Launch a NEW general-purpose subagent with the referee prompt. Inject BOTH:
+- The Hunter's full bug report
+- The Skeptic's full challenge report
+
+The Referee must independently read the code to make final judgments.
+
+Wait for the Referee to complete and capture its full output.
+
+### Step 6: Present the Final Report
+
+Display the Referee's final verified bug report to the user. Include:
+1. The summary stats
+2. The confirmed bugs table (sorted by severity)
+3. Low-confidence items flagged for manual review
+4. A collapsed section with dismissed bugs (for transparency)
+
+If zero bugs were confirmed, say so clearly — a clean report is a good result.