One-click install
npx skills add https://github.com/ncukondo/reference-manager --skill review-task-ncukondo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-task
Source: https://github.com/ncukondo/reference-manager/tree/main/.claude/skills/review-task
Command: npx skills add https://github.com/ncukondo/reference-manager --skill review-task-ncukondo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a task file to ensure all implementation steps and tests are present and aligned with acceptance criteria, reducing review overhead and drift.

Core Features & Use Cases

  • Validates completion status of steps in a task.
  • Checks test coverage and end-to-end test existence.
  • Useful for PR reviews in task-driven projects and education settings.

Quick Start

Run a full review against the target task to verify completion, tests, and acceptance criteria.

Frequently Asked Questions about review-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify implementation steps and test coverage against acceptance criteria in a task file?

To verify implementation steps and test coverage against acceptance criteria, you can review a task file by comparing it to defined specs to identify missing steps and enforce linting, typechecking, and end-to-end validation before merging changes.

What is the best way to enforce lint, typecheck, and e2e validation before a PR merge?

The best way to enforce lint, typecheck, and e2e validation before a PR merge is to run a full review against the target task, ensuring all completion statuses, tests, and acceptance criteria are aligned.

Can I use task file review for PR reviews in educational programming projects?

Yes, you can use task file review for PR reviews in educational programming projects, as it targets task-based repositories and educational settings where verification, linting, typechecking, and end-to-end validation must be tracked.

How does comparing a task file to defined specs reduce review overhead?

Comparing a task file to defined specs reduces review overhead by automatically identifying missing implementation steps and test coverage, ensuring alignment with acceptance criteria and preventing project drift.

Do I need specific dependencies to check test coverage and e2e test existence in a task repository?

No specific dependencies are required to check test coverage and e2e test existence in a task repository, as the review process operates directly on the task file and its defined specs.

Why does my task file review report missing end-to-end validation steps?

Your task file review reports missing end-to-end validation steps because it compares your task file to defined specs to identify any incomplete implementation steps, test coverage gaps, or unverified acceptance criteria.