session-retrospective

星标1

分支0

更新时间2026年7月18日 18:52

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 页面并帮你完成安装。

来源

bamr87

bamr87/lifehacker.dev

打开 GitHub 仓库查看创作者相关仓库

下载

session-retrospective — write down what the thread learned

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.

1. Pick the thread

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.

2. Read the thread honestly

Read the transcript at 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.
Extract only what really happened. Never invent a lesson, a number, a fix, or an outcome. If you can't verify it from the transcript, it does not go in — the same honesty rule the content factory runs on.

3. Draft the Field Note

One file: 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).
Frontmatter like the other field notes: 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.
Voice: first person, honest, specific, a little self-aware — mirror 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.
A structure that works: what the shift was → the part that surprised you → the concrete lessons (name the real gotcha) → what you want the next thread to know.
Redaction (hard): never quote a secret, token, key, or full credential, even if it appears in the transcript. Refer to it by name (FLEET_TOKEN), never value.

4. Record + open the PR

ruby scripts/retro/process_queue.rb --mark <session_id> <post-slug> "<title>" appends to _data/retrospectives.yml so the thread is not re-proposed.
Verify the build (bundle exec jekyll build, or the safe-mode build) and that lint_brand is clean.
Open ONE PR (branch retro/<date>-<slug>): the post + the ledger line. Title it retro: <thread, in a phrase>. Then stop.

Hard rules

Content + ledger only: 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.

同仓库更多 Skills

同仓库

grow-lifehacker

bamr87/lifehacker.dev

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.

2026-07-201

content-import

bamr87/lifehacker.dev

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.

2026-07-181

content-reviewer

bamr87/lifehacker.dev

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.

2026-07-181

content-scout

bamr87/lifehacker.dev

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.

2026-07-181

theme-scout

bamr87/lifehacker.dev

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.

2026-07-181

agent-skill-review

bamr87/lifehacker.dev

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.

2026-07-171

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.

session-retrospective — write down what the thread learned

1. Pick the thread

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.

2. Read the thread honestly

Read the transcript at 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.
Extract only what really happened. Never invent a lesson, a number, a fix, or an outcome. If you can't verify it from the transcript, it does not go in — the same honesty rule the content factory runs on.

3. Draft the Field Note

One file: 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).
Frontmatter like the other field notes: 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.
Voice: first person, honest, specific, a little self-aware — mirror 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.
A structure that works: what the shift was → the part that surprised you → the concrete lessons (name the real gotcha) → what you want the next thread to know.
Redaction (hard): never quote a secret, token, key, or full credential, even if it appears in the transcript. Refer to it by name (FLEET_TOKEN), never value.

4. Record + open the PR

ruby scripts/retro/process_queue.rb --mark <session_id> <post-slug> "<title>" appends to _data/retrospectives.yml so the thread is not re-proposed.
Verify the build (bundle exec jekyll build, or the safe-mode build) and that lint_brand is clean.
Open ONE PR (branch retro/<date>-<slug>): the post + the ledger line. Title it retro: <thread, in a phrase>. Then stop.

Hard rules

Content + ledger only: 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.