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/posting.md
View on GitHub# Post the body
Prepare the complete body and artifacts before publishing to the requested destination under existing authorization.
Use the parent skill's marked section and state comment.
Before upload, reference local artifacts through absolute paths in the body file.
Place each video in its own paragraph.
Inside details elements, keep a blank line after the summary and before the closing tag.
If installed gh supports attachments, use:
```bash
gh pr create --title '<title>' --body-file <artifact-directory>/body.md --attach <artifact-directory>/after.svg
gh pr edit <number> --body-file <artifact-directory>/body.md --attach <artifact-directory>/after.svg
```
Add the video as another attachment when present.
Otherwise, use an already-authorized upload route or return completed files to the user.
Never publish unresolved local paths.
An attach command can store some uploads before it fails.
If the PR does not exist after a failure, run the create command again.
If it exists, read its body.
If the body holds your section, upload only the files whose local paths remain and replace those paths.
Otherwise, nothing was written: build the body again from that read and run the edit again.
If a file still fails to upload, remove its local path and report the missing artifact.
For updates, read the existing body before replacing the marked section.
Read it again immediately before the write, and build the new body from that latest read.
If the marked section changed since your first read, fold that edit into your section, then read again.
Preserve author and reviewer text outside it.
Replace the section rather than appending another description.
Remove earlier generated Summary or Evidence duplicates outside the markers, while preserving unrelated author text.
Read the posted body back.
Make sure that the markers occur once, pictures use uploaded URLs, and each video URL occupies its own paragraph.
Report unavailable artifacts or history publication through the parent skill's handoff rules.
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 |