17th-task-validator

Validate git staged changes against a TASK.md task plan.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-task-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 17th-task-validator
Source: https://github.com/SeventeenthEarth/glm-worker-mcp/tree/main/skills/17th-task-validator
Command: npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-task-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers ensure their git staged changes align with the requirements defined in a TASK.md or a specified task file, preventing misalignment before commits or reviews.

Core Features & Use Cases

  • Staged-change validation: Compares staged diffs against task requirements and surfaces gaps.
  • Flexible task sources: Works with TASK.md by default or any custom task file path.
  • Pre-commit and PR readiness: Useful during pre-commit checks, code review prep, and progress tracking to verify compliance.

Quick Start

Use the 17th-task-validator to validate the current git staged changes against TASK.md or a specified task file. Provide the path to the task file if different from TASK.md, for example: task_file=PATH/TO/TASK.md

Frequently Asked Questions about 17th-task-validator

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

FAQPage Schema
How do I validate git staged changes against a task plan before committing?

To validate staged changes against a task plan, compare the Git index to your TASK.md requirements to ensure conformity before commits. This pre-commit check inspects staged diffs and outputs a structured validation report surfacing any gaps or misalignments.

What is staged-change validation for pre-commit checks?

Staged-change validation for pre-commit checks is the process of comparing your Git index against task requirements to prevent misalignment. It inspects staged diffs, verifies compliance with a task file, and generates a structured validation report before code reviews or commits.

Can I use a custom task file instead of TASK.md for validating staged git changes?

Yes, you can use a custom task file instead of TASK.md for validating staged git changes. You simply provide the specific path to your task file, and the validator will compare the Git staged changes against those custom requirements during the pre-commit check.

When do I need to verify staged diffs against task requirements?

You need to verify staged diffs against task requirements during pre-commit checks, PR preparation, and progress reviews. This ensures your staged changes align with the TASK.md file, preventing misalignment and surfacing compliance gaps before finalizing a commit or review.

What's the best way to check staged changes for task compliance before a PR?

The best way to check staged changes for task compliance before a PR is to inspect the Git index and compare staged diffs against TASK.md. This validation process outputs a structured report detailing any gaps, ensuring your staged changes meet all task requirements.