Menu
When an investigation surfaced a *separate* bug worth reporting (not the issue under investigation, but one discovered along the way), draft a fresh GitHub issue for it. SKIP when no separate bug is in the artifact. The operator approves before posting.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Filter recent Hacker News for live threads on June's topics and hand him the list. Separately, flag the rare subset where work he has already done settles a specific quoted claim, and draft that comment as a plain argument with no link to his own writing. Use when June asks to check HN or find threads worth reading or commenting on.
Scan blog posts for AI writing tics and missed opportunities for human voice. Reports subtractions (AI patterns to remove) and additions (wordplay, arc, and claims to strengthen).
Poll June's Hacker News feeds, report what is new since the last run, and idempotently arm a background watch for replies to his comments. State persists in ~/Documents/sweep/ so it survives across sessions. Use when June asks what is new on HN, whether anyone replied, or to start watching a thread.
Argument-level compression by a strengthened absence test (does the argument stand with the same force, clarity, evidence, scope, pacing, and misreading-resistance?). Removes passages that fail it (self-referential cruft, cross-section restatement, self-recap, re-derivation, scaffolding, expired reader-orientation, stakes inflation, inert hedges, redundant examples); grafts good rhetoric onto an adjacent essential point rather than deleting. Idempotent. The structural cousin of /tighten (word-level) and /not-but (negation).
Audit a technical candidate's resume/CV by verifying its claims against the public contribution graph instead of taking the text at face value. Sorts every claim onto the self/peer/world attestation lattice, applies a cost-and-stake filter so cheap proxies (stars, downloads, backlinks) don't count, runs LIVE checks (GitHub, arXiv, package registries, CVEs), and reports two separate axes โ merit (staked acceptance of the candidate's specific work) and attention (timestamped output) โ plus a verifiability score in [0,1]. For technical recruiters and hiring managers. Invoke when given a candidate โ a GitHub handle, a resume/CV, an arXiv author, a personal site โ and asked to verify, audit, vet, or check their claims. Runs at two depths โ a quick triage scan or a deep per-claim audit โ and elicits which. Checks the provenance of a personal site or self-hosted resume (Internet Archive + git history) as an un-backdatable anti-tailoring anchor. Needs tool access (Bash/curl or WebFetch).
Find and defuse "not X but Y" / "isn't X; it's Y" / "X โ not Y" constructions. Deterministic grep for detection (no LLM blind spot), the not-but subagent for triage. Split-or-cut tail negations ("X, not Y") aggressively โ promote the point to its own sentence or delete it; recast in place only mid-clause "not X but Y" that genuinely can't be split; keep just the rare iconic thesis line literal.
| name | file-issue |
| description | When an investigation surfaced a *separate* bug worth reporting (not the issue under investigation, but one discovered along the way), draft a fresh GitHub issue for it. SKIP when no separate bug is in the artifact. The operator approves before posting. |
| argument-hint | <owner/repo>#<source_issue> |
| allowed-tools | Read, Bash |
You were invoked on a source investigation โ <owner>/<repo>#<source_issue>. The hypothesis graph at repo-hypotheses/<owner>__<repo>__<source_issue>.md may contain a finding about a different bug discovered during that investigation. Your job:
A fresh issue earns the maintainer's attention only if the artifact provides something they don't already have. From floor upward:
If the artifact gives none of these โ just notices that "something else seems off" โ SKIP. A vague "FYI you might have another bug" tax on the maintainer is worse than silence.
| Requirement | Why |
|---|---|
| Lead with the failure | One sentence: what breaks, when, where. No preamble. |
| Include reproducer | The minimum โ steps, command, script. The reason for filing. |
| Cite evidence | Link the upstream PR / commit / file / line that grounds the claim. |
| Defer on the fix | If you have a fix shape, mention it as "possible direction" not "you should." |
| Stay under 250 words | Issues read in the maintainer's inbox; budget accordingly. |
| Use the project's tone | Mirror neighboring issues' voice if you can sample them. |
Print the drafted title and body as fenced blocks, title first:
<<<ISSUE_TITLE
Concise one-line title โ what breaks, optionally where
TITLE>>>
<<<ISSUE_BODY
## Description
What goes wrong, in one or two sentences.
## Reproducer
exact command or script
## Evidence
- Link to upstream PR / file / commit
- Specific line citation
- Logs if relevant
## Possible direction (optional)
If you have a clear fix shape, name it. Otherwise omit this section.
โ Filed automatically based on investigation of <owner>/<repo>#<source_issue>; please close or reassign as needed.
BODY>>>
If the artifact lacks anything from the value hierarchy, output a SKIP:
<<<ISSUE
SKIP: <one-line reason>
ISSUE>>>
The wrapper treats SKIP as "discard this card."
Good draft (root cause + reproducer):
<<<ISSUE_TITLE
Cache invalidation skipped when entry size exceeds 64KB
TITLE>>>
<<<ISSUE_BODY
## Description
While investigating #12345, found a separate bug: the LRU cache silently skips invalidation for entries larger than 64KB, causing stale reads across restarts.
## Reproducer
```bash
python -c "from foo.cache import Cache; c=Cache(); c.put('k', 'x'*100_000); c.invalidate('k'); print(c.get('k'))"
# prints 'xxx...' instead of None
foo/cache.py:142 โ if len(value) < SIZE_LIMIT: del self._store[k]The size check appears to be guarding storage, not eviction. Removing it from invalidate() (line 142) while keeping it in put() (line 87) would likely fix.
โ Filed automatically based on investigation of foo/bar#12345; please close or reassign as needed. BODY>>>
When in doubt, SKIP. Fresh issues create triage burden; the bar is high.