Devex and documentation review
Skill wfprieto/wcbs-build-kit/skills/devex-and-documentation-review
Use when changes affect developer experience, setup, commands, documentation, README files, examples, onboarding, API docs, release notes, handoffs, or maintainability of instructions. Reviews docs for accuracy, discoverability, task fit, redaction, and APIVR evidence alignment.From its SKILL.md
npx -y skills add wfprieto/wcbs-build-kit --skill devex-and-documentation-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.6 KB, as published. Nobody here has run it
DevEx And Documentation Review
Use this skill for developer-facing workflows and durable docs.
Review Protocol
- Identify the reader and job: installer, maintainer, reviewer, operator, integrator, or future agent.
- Verify commands are current and runnable or clearly marked unverified.
- Check that docs reference canonical files instead of duplicating stale instructions.
- Confirm secrets, tokens, and private data are redacted.
- Ensure handoffs reference artifacts and evidence instead of replaying chat memory.
- For provider-facing routes, confirm docs name the route contract, deployed callback URL, provider account/environment, sandbox/live values, deployment-protection expectation, replay/idempotency behavior, and exact verification evidence.
- Apply
skills/20-pass-protocol/SKILL.mdto high-stakes runbooks, setup instructions, release notes, prompts, agent handoffs, and accuracy-critical docs. - Classify evidence state for every claim that affects setup, release, or operation.
Documentation Types
- Tutorial: teach first successful path.
- How-to: solve a concrete task.
- Reference: list exact contracts, commands, config, schemas, or APIs.
- Explanation: document decisions, tradeoffs, and architecture.
Worked Example
Scenario: A new webhook integration changes env vars and retry behavior.
- DevEx review requires
.env.exampleupdate, provider setup notes, route contract, deployed callback URL, local replay command, safe logging note, and rollback section. - Claims about provider behavior are
Likelyuntil sandbox replay is run. - Completion report links docs changed and evidence state.
Workflow
Follow the documented first-use path in a clean fixture, correct the smallest friction point, and verify that setup, examples, and handoff stay aligned.