quest-forge

Sterne1

Forks0

Aktualisiert17. Juli 2026 um 14:45

After a retrospective is published, capture the merged-branch metadata of the build it covers and derive an it-journey.dev epic quest (or quest-chapter) from it — filing ONE proposal issue to bamr87/it-journey with the full plan and commit-hash references. Read-only on lifehacker.dev; files nothing here; never merges.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

bamr87

bamr87/lifehacker.dev

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Sonstige ComputerberufeInformatik- und Mathematikberufe·SOC 15-1299

SKILL.md

readonly

name	quest-forge
description	After a retrospective is published, capture the merged-branch metadata of the build it covers and derive an it-journey.dev epic quest (or quest-chapter) from it — filing ONE proposal issue to bamr87/it-journey with the full plan and commit-hash references. Read-only on lifehacker.dev; files nothing here; never merges.

quest-forge — turn a finished build into a gamified quest

The last stage of the retrospective chain. A thread's work has merged and its retrospective is published; this turns the metadata of those merged branches into an it-journey.dev quest, so the build becomes a learnable, gamified journey. The issue is a proposal — a human on it-journey accepts, adapts, or declines it.

1. Capture the metadata (systematic, deterministic)

ruby scripts/retro/collect_merged.rb --markdown → the full ledger (PR number, squash-merge SHA, date, size, branch, title). Scope to the new work with --since <date> — the previous entry's published date in _data/retrospectives.yml. Use all of it on the first/bootstrap run.

2. Derive the quest (match it-journey's format)

it-journey gamifies IT learning as RPG quests. Match its conventions:

Tiers (binary levels): 🌱 Apprentice 0000–0011 · ⚔️ Adventurer 0100–0111 · 🔥 Warrior 1000–1011 · ⚡ Master 1100–1110 · 👑 Legend 1111.
Difficulty: 🟢 Easy · 🟡 Medium · 🔴 Hard · ⚔️ Epic. XP: 20–150 per quest.
Classes: Software Developer · System Engineer · Security Specialist · Data Scientist · Digital Artist · Game Developer. Types: main_quest / side_quest / epic_quest.
Badges: e.g. First Pull Request, Bug Slayer, Security Guardian.

Group the merged branches into themed chapters (milestones a learner can reproduce). Each chapter: a tier+level, difficulty, XP, class, the PRs + commit hashes it maps to, and a concrete "what you learn." Name a boss fight from the hardest bug; award badges. Keep the fantasy-infused but honest tone.

3. File ONE proposal issue to it-journey

gh issue create --repo bamr87/it-journey --title "⚔️ Epic Quest: …" --label enhancement --label automated --body-file …
Include: the premise, a quest-metadata block, the chapter series with hashes, the badges, a build plan for maintainers, and the full ledger table.
Cross-link lifehacker commits as bamr87/lifehacker.dev@<sha> and PRs as bamr87/lifehacker.dev#<n>.
Idempotency: if an open quest issue already covers this build/window, comment an update instead of filing a duplicate. If there's no substantial new build since the last retrospective, file nothing and say so. If you cannot file cross-repo (no it-journey token), print the full issue body to the log instead.

Hard rules

READ-ONLY on lifehacker.dev — never edit this repo, never merge. Capture metadata only; quote real PR numbers and commit hashes (never invent one). The it-journey issue is a proposal, not a change. ONE issue per run.

Mehr aus diesem Repository

gleiches Repository

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

session-retrospective

bamr87/lifehacker.dev

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.

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

name	quest-forge
description	After a retrospective is published, capture the merged-branch metadata of the build it covers and derive an it-journey.dev epic quest (or quest-chapter) from it — filing ONE proposal issue to bamr87/it-journey with the full plan and commit-hash references. Read-only on lifehacker.dev; files nothing here; never merges.

quest-forge — turn a finished build into a gamified quest

1. Capture the metadata (systematic, deterministic)

ruby scripts/retro/collect_merged.rb --markdown → the full ledger (PR number, squash-merge SHA, date, size, branch, title). Scope to the new work with --since <date> — the previous entry's published date in _data/retrospectives.yml. Use all of it on the first/bootstrap run.

2. Derive the quest (match it-journey's format)

it-journey gamifies IT learning as RPG quests. Match its conventions:

Tiers (binary levels): 🌱 Apprentice 0000–0011 · ⚔️ Adventurer 0100–0111 · 🔥 Warrior 1000–1011 · ⚡ Master 1100–1110 · 👑 Legend 1111.
Difficulty: 🟢 Easy · 🟡 Medium · 🔴 Hard · ⚔️ Epic. XP: 20–150 per quest.
Classes: Software Developer · System Engineer · Security Specialist · Data Scientist · Digital Artist · Game Developer. Types: main_quest / side_quest / epic_quest.
Badges: e.g. First Pull Request, Bug Slayer, Security Guardian.

3. File ONE proposal issue to it-journey

gh issue create --repo bamr87/it-journey --title "⚔️ Epic Quest: …" --label enhancement --label automated --body-file …
Include: the premise, a quest-metadata block, the chapter series with hashes, the badges, a build plan for maintainers, and the full ledger table.
Cross-link lifehacker commits as bamr87/lifehacker.dev@<sha> and PRs as bamr87/lifehacker.dev#<n>.
Idempotency: if an open quest issue already covers this build/window, comment an update instead of filing a duplicate. If there's no substantial new build since the last retrospective, file nothing and say so. If you cannot file cross-repo (no it-journey token), print the full issue body to the log instead.

Hard rules

READ-ONLY on lifehacker.dev — never edit this repo, never merge. Capture metadata only; quote real PR numbers and commit hashes (never invent one). The it-journey issue is a proposal, not a change. ONE issue per run.