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/split.md
View on GitHub# Choose review boundaries
Use this reference only under the parent skill's delivery authorization rules.
Module count alone never determines PR count.
For authorized branch operations, use the installed gh-stack skill.
Read the whole diff, intended behavior, and proposal comparison.
Choose layers that ship independently with clear contracts and focused evidence.
Keep coupled APIs, callers, and required data transitions together when separation creates an unusable state.
Tests belong with their implementation. Documentation belongs with its behavior.
Name each layer's result and dependencies.
If a layer exists only because a diagram shows another module, keep it in the integration PR.
If no independent benefit remains, stop splitting.
Present the proposed PRs, their contents, order, and dependencies to the user.
Wait for explicit confirmation of that split before creating or restructuring branches, moving commits, or opening separate PRs.
Permission to explore a split does not authorize carrying it out.
For each layer, record model, stable state ID, exact predecessor, and comparison base.
A proposal can span modules and flows.
Never derive proposal ancestry from branch names.
For a partial implementation of a larger design, follow [reconciliation](reconcile.md).
Retain exact comparison evidence per review boundary.
For one integration PR, keep work on its branch and use commits as progress points.
Explain broad work through several scopes or walkthrough beats in its Summary.
For an authorized stack, use the actual lower branch as each PR's base.
Make sure that every layer works with its dependencies and has focused evidence.
Use the parent skill's body and adoption workflow for each PR.
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 |