ln-402-task-reviewer

Review task implementations for quality, standards, and test coverage.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-402-task-reviewer-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-402-task-reviewer
Source: https://github.com/0xtaoist/taogate/tree/main/ln-402-task-reviewer
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-402-task-reviewer-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews and assures quality for a single task implementation, enforcing standards, tests, and safety checks, while surfacing actionable fixes and rework notes.

Core Features & Use Cases

  • Mandatory post-task review to decide Done or To Rework with explicit fixes.
  • AC validation via the ac_validation_checklist ensuring completeness, specificity, dependencies, and DB scope.
  • Side-effect detection that creates separate [BUG] tasks for issues found outside the current task's scope.
  • Mechanical verification (lint/typecheck) run when the task is Done to ensure pipeline safety.
  • Comprehensive plan-context loading including task and parent Story to verify alignment and traceability.

Quick Start

Provide a taskId to initiate the post-task review, and the skill will load context, apply checks, and return a Done or To Rework decision with recommended fixes.

Frequently Asked Questions about ln-402-task-reviewer

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

FAQPage Schema
How do I automate code review and quality checks for a single task implementation?

Automated task quality review loads the task context and parent Story, applies architecture and documentation checks, validates acceptance criteria, and returns a Done or To Rework decision with explicit fixes.

What is the best way to track side-effect bugs found during a code review?

Side-effect bug tracking during code review identifies issues outside the current task scope and automatically generates separate [BUG] tasks to flag them for resolution.

How do I validate acceptance criteria and destructive-operation guards before marking a task as Done?

AC validation and safety checks ensure completeness, specificity, and DB scope, while enforcing destructive-operation guards to verify pipeline safety before a task is marked Done.

Can I run mechanical verification like lint and typecheck during automated task review?

Mechanical verification runs lint and typecheck when the automated task review decides a task is Done, ensuring code standards and pipeline safety are met.

Does automated task review require loading the parent Story context?

Automated task review requires loading the task context and its parent Story to verify alignment, traceability, and comprehensive plan context before applying quality gates.

What happens if a task fails safety and quality gates during automated review?

When a task fails safety and quality gates, the automated review returns a To Rework decision with explicit fixes and recommended rework notes to address the identified issues.