From theclauu
Use when the agent spots follow-up work during an existing PR that is out-of-scope for the current work. Files a GitHub Issue tagged `discovered-by:theclauu`, backlinked to the current PR. Auto-promotes to Linear on PR merge (Slice 3 GH Action).
npx claudepluginhub artemis-xyz/theclauu --plugin theclauuThis skill uses the workspace's default tool permissions.
Engineer-facing workflow for the **discovered work** path. Distinct from the
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Engineer-facing workflow for the discovered work path. Distinct from the
analyst-facing file-github-issue skill (which is for bug reports with
screenshots). This one is for the agent, mid-PR, spotting something that
doesn't belong in the current change.
File automatically (no prompt):
Surface to user first (let them decide):
Never file (either fix or drop):
<repo>: accepts bare name (dbt) or full slug (Artemis-xyz/dbt). Bare resolves to Artemis-xyz/<name>.<title>: short, actionable. Imperative form. No trailing punctuation.<body>: optional. If omitted, derive from the agent's current context.If <repo> or <title> missing, ask the user. Don't guess.
Always search for existing issues first:
gh issue list --repo <repo> --state open --search "<keywords-from-title>" --json number,title,url,labels
If a similar open issue exists:
Match heuristic: ≥3 distinctive tokens overlap between titles (post-stopword). Ask the user when in doubt.
Template:
**Discovered during:** <PR URL> (or `<branch>` if no PR yet)
**What to do:** <brief description>
## Context
<agent's analysis of what should change, where, and why>
## Why not in the current PR
<one sentence: out-of-scope, different concern, different area, etc.>
Always include the "Discovered during" backlink. This is what the Slice 3 auto-promotion action reads.
gh issue create \
--repo <repo> \
--title "<title>" \
--body "<body>" \
--label "discovered-by:theclauu"
Then print the URL and the issue number.
If the user passed --skip-linear, also add the skip-linear label:
gh issue edit <number> --repo <repo> --add-label "skip-linear"
This tells the Slice 3 GH Action to leave the issue alone on PR merge.
Append a minimal record to ~/.theclauu/session-issues.json (create if missing) so the Stop hook knows what the session filed:
[{"repo": "Artemis-xyz/dbt", "number": 1234, "url": "..."}]
The auto-trigger nudge (Stop hook) uses this to avoid double-prompting the engineer about the same issues.
Output format:
Filed: <repo>#<number> — <title>
URL: <url>
Label: discovered-by:theclauu (auto-promotes to Linear on PR merge)
If commented on existing issue instead:
Commented on: <repo>#<number> — <existing-title>
URL: <url>
(dedup match — did not create a new issue)
Every issue filed with discovered-by:theclauu gets picked up by the GH
Action in the target repo when the spawning PR merges. The Action creates a
Linear TODO ticket with:
LINEAR_API_TOKEN secret)auto-promoted, plus repo nameThe GH issue then closes with a linear:ART-NNNN back-reference label. See
wiki/decisions/2026-04-22-four-tier-knowledge-model.md in the data-hive-mind
wiki.
skip-linear is intended — use the flag, don't skip the flow entirely./theclauu:linear — the other work-capture skill, for intentional (not discovered) work starting fresh./theclauu:file-github-issue — analyst-facing sibling for bug reports with screenshots.