verify-readme-features
Verify README Features
You are helping the user verify that every feature claim in their project's README (or similar documentation file) is backed by actual implementation in the codebase.
When to Use
- After updating a feature list in documentation
- Before a release, to ensure docs match reality
- When onboarding to a project and wanting to trust the README
- When refactoring or removing features that may still be documented
Verification Process
Step 1: Identify Feature Claims
- Read the documentation file (default:
README.mdin the project root) - Extract each feature claim — every bullet point, heading, or sentence that describes a capability of the project
More from rlespinasse/agent-skills
diataxis
Helps maintain documentation pages based on the Diataxis method. Analyzes existing docs, classifies pages into tutorials/how-to/explanation/reference categories, identifies gaps, and helps create or restructure documentation following Diataxis principles. Use when user mentions documentation structure, Diataxis, doc categories, tutorials vs how-to guides, or reorganizing docs.
41drawio-export-tools
Decision guide for the third-party Draw.io export ecosystem by @rlespinasse. Covers docker-drawio-desktop-headless (base Docker), drawio-exporter (Rust backend), drawio-export (enhanced Docker), and drawio-export-action (GitHub Actions). Use when user mentions diagram export, CI/CD automation, batch processing, or Draw.io files. Helps select the right tool based on context.
24conventional-commit
Guides committing staged (indexed) git files using the Conventional Commits specification
21pin-github-actions
Migrates GitHub Actions workflows to use pinned commit SHAs instead of
15verify-pr-logs
Checks GitHub Actions CI logs on a pull request, diagnoses failures,
7french-language
Ensures all project content is written in proper French with correct accents, grammar,
6