post-dev-recap SKILL.md skillA
post-dev-recap from sd0xdev/sd0x-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sd0xdev/sd0x-harness/post-dev-recap@git:20260905.d98c025Pins git:20260905.d98c025 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sd0xdev/sd0x-harness
- Path
skills/post-dev-recap/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260905.d98c025, committed Sep 5, 2026
- First version recorded
- Apr 17, 2026
- Size
- 14,791 bytes
- Repository stars
- 194
- License
- MIT
Post-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (use /tech-brief), first-principles reasoning of an existing doc (use /fp-brief), general code tracing (use /code-explore). Output: ScopeReport → briefing-recap-<date>.md → interactive Q&A session.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# `/post-dev-recap` — Guided Post-Development Recap ## Trigger - Keywords: post-dev-recap, 開發後導覽, walkthrough after dev, recap workflow, 本輪回顧 ## When NOT to Use | Scenario | Alternative | |----------|------------| | Only need a doc (no Q&A) | `/recap-doc` — emits the recap markdown and stops | | Have an existing recap, want to ask questions | `/recap-ask --context <path>` | | Share-out for other developers (not the author) | `/tech-brief` — focuses on knowledge transfer to strangers | | First-principles reasoning of an existing doc | `/fp-brief` — explains *why* decisions hold | | General project Q&A, no recent change | `/ask` — reopens the whole repo as context | | Deep code tracing across modules | `/code-explore` — execution-path walker | ### Positioning vs `/ask`, `/tech-brief`, `/fp-brief`, `/code-explore` (AS-5) | Dimension | `/post-dev-recap` | `/ask` | `/tech-brief` | `/fp-brief` | `/code-explore` | |-----------|-------------------|--------|----------------|-------------|-----------------| | **Trigger** | Right after AI/Codex finishes a feature | Any quick question | Share-out for teammates | Explain an existing doc | Diagnose unknown code | …
Read the whole file at its exact version.
How to install
mdr add sd0xdev/sd0x-harness/post-dev-recap@sha256:68674e1485b6bdb3The line at the top of this page pins the label git:20260905.d98c025, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_y4nj53mul2b35ffb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 17, 2026 and Sep 5, 2026, about one every 71 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.d98c025 latest | 2026-09-05 | d98c025 | 14,791 B | A | view · diff |
| git:20260811.d9a8bca | 2026-08-11 | d9a8bca | 14,835 B | A | view · diff |
| git:20260417.e56f168 | 2026-04-17 | e56f168 | 14,250 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14791 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
sd0xdev/sd0x-harness · 194 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_y4nj53mul2b35ffb GET https://markdownregistry.com/api/v1/resolve?ref=sd0xdev/sd0x-harness/post-dev-recap GET https://markdownregistry.com/api/v1/blob/68674e1485b6bdb39af3b6f12334825f7e6db3b1a7168ef15498e090610d4dd0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.