skyosev/party-hunter-go

Party Hunter — Go

Orchestrate a full audit of a Go codebase by running all 10 hunter skills as independent subagents, each producing a focused report. Results land in a single timestamped folder for easy review and sharing.

Execution Protocol

1. Ask for scope

If the user has not specified a target (file, package path, or directory), ask before proceeding. Do not guess — the hunters need a concrete scope to be useful.

2. Create the reports folder

reports/party-hunter-go/YYYY-MM-DDTHHMM/

Use the current timestamp. Create the folder before launching any subagents.

3. Launch all hunters as subagents

Run all 10 subagents in parallel. Pass the same target scope to each. Each subagent must load its hunter skill and return findings as a Markdown report.

| Hunter | Skill to load | Output file | |--------------|-------------------------|-------------------| | Boundary | boundary-hunter-go | boundary.md | | Doc | doc-hunter-go | doc.md | | Invariant | invariant-hunter-go | invariant.md | | Security | security-hunter-go | security.md | | Simplicity | simplicity-hunter-go | simplicity.md | | Slop | slop-hunter-go | slop.md | | Smell | smell-hunter-go | smell.md | | SOLID | solid-hunter-go | solid.md | | Test | test-hunter-go | test.md | | Type | type-hunter-go | type.md |

Subagent prompt template (adapt per hunter):

Load and apply the {skill-name} skill to the Go code at {target_scope}.
Produce a structured Markdown report with:
- An executive summary (2-3 sentences)
- Findings grouped by severity (Critical / High / Medium / Low)
- For each finding: location, description, and a concrete fix suggestion
Return only the Markdown report — no commentary outside the report.

4. Write report files

As each subagent completes, write its output to the corresponding file inside the reports folder. Do not wait for all subagents before writing — write as results arrive.

5. Write summary

After all 10 subagents have finished, write summary.md to the same folder:

# Party Hunter Report — Go
**Target**: {target_scope}
**Date**: {timestamp}

## Hunter Results

| Hunter     | Critical | High | Medium | Low | Total |
|------------|----------|------|--------|-----|-------|
| Boundary   | …        | …    | …      | …   | …     |
| …          |          |      |        |     |       |

## Cross-cutting Themes
{2-4 recurring patterns observed across multiple hunters}

## Top 5 Priority Issues
{Ranked list of the most impactful findings regardless of hunter}

Output Contract

Every report file must be valid Markdown. Finding counts in summary.md must match the findings in individual reports. If a hunter finds nothing, write a one-line note (No findings.) rather than an empty file.