Menú
Find theme UI/UX + accessibility issues and upstreamable local fixes in lifehacker.dev, and file deduped issues upstream to bamr87/zer0-mistakes so the site can focus on content.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | theme-scout |
| description | Find theme UI/UX + accessibility issues and upstreamable local fixes in lifehacker.dev, and file deduped issues upstream to bamr87/zer0-mistakes so the site can focus on content. |
lifehacker.dev runs on bamr87/zer0-mistakes as a remote theme. Your job is to make the THEME better by finding real contributions and filing them upstream — so this repo stays focused on content, and every other site using the theme benefits too. You file issues on bamr87/zer0-mistakes. You never edit lifehacker.dev content, never merge, never close anyone's issue.
Two kinds, both about the theme, not the content:
scripts/ci/build.sh, the build-overlay action,
_config.yml / _config_dev.yml, scripts/explorer/* (the self-healing sitemap), _data/theme_*.yml, _includes/ overrides.curl -s https://lifehacker.dev/ and /news/ /news/hacks/ /news/tools/ /news/field-notes/ /docs/ /about/colophon/ — inspect the theme-rendered HTML/CSS.scripts/ci/check_drift.rb,
htmlproofer_check.rb, anything the triage routed route_to: upstream, _data/health/queue.json.gh issue list --repo bamr87/zer0-mistakes --state all --search "<keyword>" (and a broad --state open list). If the issue already exists, SKIP it. Never create a duplicate.file:line or a specific
live-site symptom) and, where lifehacker.dev already solved it, the working fix.apply is set; otherwise print what you would file):
gh issue create --repo bamr87/zer0-mistakes --title "..." --body "...".
fix: / feat: / a11y:).--max-issues, default 5) — quality over volume.bamr87/zer0-mistakes ONLY. Never open issues/PRs against lifehacker.dev
content from here, never edit content, never merge, never close an issue..claude/skills/_shared/quarantine.md).The autopilot engine for lifehacker.dev. Use when asked to "grow the site", "run the autopilot", "publish the next thing", "do an autopilot run", or to produce a new hack / tool review / field note. Reads the brand + backlog, drafts on-voice content with screenshots, files upstream bugs, and opens a PR for human review. Never pushes to main, never self-merges.
The repeatable flow for importing and REWRITING external/legacy articles into on-voice lifehacker.dev content. Use when asked to "import these posts", "rewrite the it-journey import", "bring in content from <source>", or to process a bulk-import PR (like #55) article-by-article. Triages every source file, routes it to the right collection, rewrites it through the content agents (never by hand), reuses preview images, preserves it-journey quest links, verifies with the harness, and opens ONE PR per collection in batches of 10. Never merges, never self-approves.
Reviews and improves a content pull request for lifehacker.dev. Use on a bot-authored content PR (hack/tool/post/doc) to analyze quality, completeness, and accuracy against the brand and the Prime Directive, apply small improvements directly to the PR, and backlog any larger ideas or follow-ups it surfaces. Comment-only on judgment calls; never merges, never self-approves.
The sister-site idea scout for lifehacker.dev. Use to "scout it-journey for ideas", "crawl the sister site for topics", "refill the content backlog from it-journey", or on a schedule before the content factory. Crawls a configured source site (it-journey.dev by default) along a seeded plan, reads pages via WebFetch, and — with no hand-picked topic — decides what fits the lifehacker.dev brand, proposing those topics into _data/backlog.yml each pinned to the source it-journey.dev page. Read-only on the source; opens ONE PR; never merges.
Turn a finished Claude Code thread into one honest, on-voice Field Note for the site — the narrative, the hard-won lessons, the durable concepts — then record it in the ledger. Reads the transcript, redacts every secret, opens one content PR, never merges.
The routine for reviewing + evaluating the repo's agents and skills — quality, consistency, least-privilege tools, overlap, and drift vs the workflows — and opening one focused improvement PR.