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/reconcile.md
View on GitHub# Align the proposal and implementation
Read the proposal and diff at their exact architecture and source revisions.
Use the parent skill's comparison, footprint, and code inspection commands.
Account for every affected subject:
- Implemented as proposed: Preserve IDs and attach actual bindings and anchors.
- Proposed but unimplemented: Keep it proposed, or record an authorized removal.
- Implemented but undescribed: Add the actual architectural change to the proposal.
Resolve design differences within existing authorization.
If a decision exceeds it, show the owner the source difference and required choice.
Continue independent work while awaiting that choice. Routine factual corrections need no repeated permission.
For standing or changed predecessors, follow the consumer reconciliation and settlement recipe across the affected family.
If the design document changed, read its diff from the referenced commit.
Update the affected meaning and document reference in one edit, preserving unrelated proposals and baselines.
A larger design can retain planned subjects while supporting a narrower implementation.
Use a dependent proposal only when its complete predecessor fits that implementation.
Use scope and focus to narrow pictures, never delete planned subjects to create a smaller picture.
Finish when the proposal matches the authorized change, document references identify its source, and affected standing is explicit.
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 |