long-task-review

Automate software implementation reviews against SRS, design documents, and UI style guides.

178|43|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: long-task-review
Source: https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-review
Command: npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the critical review process to ensure that implemented code strictly adheres to approved specifications, design documents, and UI style guides before being committed. It prevents deviations and maintains project integrity.

Core Features & Use Cases

  • Automated Compliance Checks: Verifies adherence to SRS, design docs, and UCD style guides.
  • Pre-Commit Validation: Runs checks after quality gates but before persisting code changes.
  • Use Case: After a feature passes automated tests, this Skill acts as a final gatekeeper, reviewing the code against the SRS and design to catch any subtle discrepancies or style violations, ensuring high-quality, consistent software.

Quick Start

Use the long-task-review skill to review the current feature's compliance with spec and design.

Frequently Asked Questions about long-task-review

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

FAQPage Schema
How do I automate code review for spec and design compliance before commit?

Automated code review for spec compliance validates implemented features against SRS, design documents, and UCD style guides. It runs pre-commit checks after quality gates to catch deviations, verify test coverage, and identify undocumented side effects before persisting code changes.

What is SRS and design document adherence validation in software engineering?

SRS and design document adherence validation is a process ensuring code implementations strictly match approved specifications and UI style guides. It prevents architectural deviations by using structured checklists with defined severity levels to maintain project integrity.

How do I verify UI feature implementation against UCD style guides?

Verifying UI features against UCD style guides requires automated checks that compare implemented code against approved user-centered design documents. This ensures all verification steps are covered by tests and no undocumented style violations or side effects exist.

Does pre-commit validation work after automated tests pass?

Pre-commit validation works as a final gatekeeper after automated tests pass. It reviews code against SRS and design documents to catch subtle discrepancies, ensuring high-quality software by validating adherence before changes are persisted.

What are the limitations of automated spec adherence checks?

Automated spec adherence checks require a structured review process with defined checklists and severity levels to function properly. They are limited to validating documented specifications and cannot assess undocumented requirements or subjective design quality outside the provided SRS and UCD.

Can I use design review checklists to catch undocumented side effects?

Design review checklists can catch undocumented side effects by systematically verifying that all implementation steps align with the SRS and design documents. This structured process ensures no deviations exist and all specified verification steps are covered by tests.