From emmaly-skills
Use when reviewing project documentation for quality, accuracy, completeness, or consistency — identifies actionable recommendations and presents each interactively
How this skill is triggered — by the user, by Claude, or both
Slash command
/emmaly-skills:doc-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematically review documentation, identify items needing attention, and interactively present recommendations for each.
Systematically review documentation, identify items needing attention, and interactively present recommendations for each.
Unless the user specifies particular files or directories:
.md files, CLAUDE.md, README.md, etc.node_modules, .git, vendor, dist, build, and other generated directories.Read each doc and identify concrete, actionable items. Only flag things that actually need addressing — don't manufacture recommendations. Categories:
For each recommendation, use AskUserQuestion to present it. Structure each question as:
(Recommended) — describe exactly what you'd changeBatching: Group up to 4 related recommendations from the same file into a single AskUserQuestion call to reduce interruptions. Start a new call for each new file or when you've hit 4 questions.
Question format: The question text should clearly state what the issue is. The option descriptions should state what the change would be.
Example:
Question: "README.md references `npm start` but the project uses `pnpm dev` — update the command?"
Option 1: "Change to `pnpm dev` (Recommended)" — description of the fix
Option 2: "Document both commands" — alternative approach
Option 3: "Skip" — leave as-is
After collecting all answers:
After all updates are applied, report:
npx claudepluginhub emmaly/emmaly --plugin emmaly-skillsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.