api-doc-review skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
api-doc-review is agent-read markdown (skill) from yeaight7/agent-powerups: Use when API documentation may have drifted from the implementation -- endpoints changed without a spec update, integration partners report mismatches, or a PR touches routes, params, or response shapes..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Purpose
Outdated API documentation causes integration failures. The code is the source of truth, and the docs must match. Review the docs against the actual route handlers and fix mismatches immediately — do not defer.
## When to Use
- A PR adds or modifies routes, request/response types, or error handling
- Consumers report behavior that contradicts the documented API
- Before publishing or versioning an OpenAPI/Swagger spec
## Inputs
- The API documentation (OpenAPI/Swagger spec, or inline route docs)
- The route handler source, types/validation schemas, and API tests
## Workflow
1. **Inventory both sides.** List documented endpoints and implemented routes, then diff the two lists:
```bash
rg -n "^ /" openapi.yaml # documented paths
rg -n "router\.(get|post|put|patch|delete)\(" src/ # implemented routes
git diff --name-only origin/main...HEAD -- "src/routes/" # what changed recently
```
2. **Verify each endpoint** (e.g., POST /users) against its route definition: path, method, and auth requirements — route middleware vs the documented security scheme.
…Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/api-doc-review@git:20260606.3196432mdr add yeaight7/agent-powerups/api-doc-review@sha256:4b1bdcc72859790ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_q3wmvolla62sesja)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.3196432 latest | 2026-06-06 | 3196432 | 3,062 B | A | view · diff |
| git:20260602.57fd736 | 2026-06-02 | 57fd736 | 705 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 (3062 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
yeaight7/agent-powerups · 6 stars · license Apache-2.0 · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q3wmvolla62sesja GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/api-doc-review GET https://markdownregistry.com/api/v1/blob/4b1bdcc72859790eb28e1789168c5db416e5fe71455cb55be5dc5e6566a0dc16
Your agent 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.
More from yeaight7/agent-powerups
Every file in yeaight7/agent-powerups