القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
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.
| name | session-retrospective |
| description | 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. |
Every finished thread is a candidate for a retrospective: a short Field Note, in the autopilot's own voice, about what was attempted, what broke, and what is worth remembering. The SessionEnd hook queues the threads; this is how you turn one into a published post. The point is institutional memory — so the next thread starts knowing what this one cost.
ruby scripts/retro/process_queue.rb --next → the newest pending thread
(session_id + transcript_path). If it prints "No pending retrospectives", stop and say so — open no PR.transcript_path (a .jsonl of the session). Skim for
the ARC, not every token: what the human asked, what you actually did, the turning points (an error → the fix), the honest failures, the few durable lessons.pages/_posts/field-notes/<YYYY-MM-DD>-<slug>.md (date = today, the
publish date). Field notes are the field-notes news section now (issue #337).title, description, date,
categories: [Field Notes], tags, author: claude, excerpt. Tag from the field-notes pill vocabulary (automation ai jekyll ci-cd satire business engineering career) — a retrospective is usually career; no one-off tags.pages/_posts/field-notes/2026-06-22-i-hired-a-robot-to-write-this-website.md. Read the brand files first (_data/brand/voice.yml, glossary.yml) and run ruby scripts/ci/lint_brand.rb before you open the PR.FLEET_TOKEN), never value.ruby scripts/retro/process_queue.rb --mark <session_id> <post-slug> "<title>"
appends to _data/retrospectives.yml so the thread is not re-proposed.bundle exec jekyll build, or the safe-mode build) and that
lint_brand is clean.retro/<date>-<slug>): the post + the ledger line. Title it
retro: <thread, in a phrase>. Then stop.pages/_posts/field-notes/** and _data/retrospectives.yml. Never
touch infra, scripts, or workflows. Never fabricate. Redact every secret. One PR per run. Never merge.