miklschmidt/archboard / skills/archboard-pr
archboard-pr
VerifiedHelp agents and humans understand architectural changes and choose meaningful PR boundaries. Use when creating PRs, updating PRs, or writing PR bodies, and load it together with any other PR skill, such as pr.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.2 KB |
| references/design.md | markdown | 1.6 KB |
| references/ephemeral.md | markdown | 2.2 KB |
| references/posting.md | markdown | 2.0 KB |
| references/reconcile.md | markdown | 1.4 KB |
| references/renders.md | markdown | 2.8 KB |
| references/split.md | markdown | 1.7 KB |
| references/walkthrough.md | markdown | 2.0 KB |
references/walkthrough.md
View on GitHub# Narrate the review
Before authoring, read the consumer walkthrough reference, including its PR narrative sequence and recording recipe.
Use the installation guide's recording prerequisites: Codex sign-in, Chromium, ffmpeg, and a matching frontend build.
For unavailable prerequisites, follow the parent skill's setup and handoff rules.
Author the walkthrough in the intended proposal, targeting its stable ID or an exact retained state.
Read the completed edit checkpoint through `model read --checkpoint <id> --walkthrough <id> --shared`.
Make sure that the selected proposal and every beat match the review.
Use the same checkpoint selection rules as [renders](renders.md).
Record and replay with the consumer recipe and explicit artifact paths:
```bash
archboard model record --checkpoint <checkpoint-id> --walkthrough <walkthrough-id> --talk <artifact-directory>/talk --out <artifact-directory>/walkthrough.mp4 -C <checkout>
archboard model replay <artifact-directory>/talk --out <artifact-directory>/walkthrough-again.mp4
```
Video and pictures use Blocks by default. The talk keeps its layout for replay.
Read the receipt's duration, output size, talk path, and exact revision.
Check the recording as the consumer reference's recording check says, before you use it.
Keep the retained narrative and talk until artifacts are complete.
For chapter times, use `architecture.playback.beats` and the `step` and final `said` entries in `events`.
Divide event sample positions by `audio.sampleRate`.
Use canonical playback metadata, not the legacy document envelope.
Copy spoken words exactly, with spacing repairs only.
Place the video below its picture in Summary, with transcript and chapter times in collapsed details.
Upload the standalone MP4 through [posting](posting.md). Keep the talk directory for replay.
For history sharing, follow the parent skill's publication step.
Removing a temporary narrative later needs a separate authorized edit and preserves its recording checkpoint.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |