task-check

Extract acceptance criteria from GitHub issues and validate code changes against them.

2|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill task-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-check
Source: https://github.com/signalbeam-io/signalbeam-edge/tree/main/.claude/skills/task-check
Command: npx skills add https://github.com/signalbeam-io/signalbeam-edge --skill task-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA check to verify that software implementations on the current branch satisfy the requirements defined by linked GitHub issues.

Core Features & Use Cases

  • Automates extraction of acceptance criteria from issues and cross-checks with code changes, tests, and documentation.
  • Serves as a gating mechanism for PRs and releases to prevent scope creep.
  • Generates a structured report with evidence suitable for audit and handoff.

Quick Start

Run the task-check skill on your feature branch or PR to auto-validate that code changes meet the linked GitHub issue's acceptance criteria.

Frequently Asked Questions about task-check

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

FAQPage Schema
How do I verify code changes meet GitHub issue acceptance criteria?

To verify code changes meet GitHub issue acceptance criteria, you can use a QA gate skill that parses issue text, classifies criteria into Must Have, Should Have, and Nice to Have, and compares them against code diffs and tests.

Can I automate scope creep prevention in pull requests using issue specs?

Yes, you can prevent scope creep in pull requests by using an automated QA gate that cross-checks feature branch code changes and documentation against the linked GitHub issue requirements, generating a structured pass or fail verdict.

How does automated acceptance criteria extraction work for release gates?

Automated acceptance criteria extraction for release gates works by parsing linked GitHub issue text, classifying requirements by priority, collecting evidence from code diffs and tests, and reporting a structured pass or fail verdict.

Do I need linked GitHub issues to validate feature branch implementations?

Yes, you need linked GitHub issues to validate feature branch implementations because the QA verification process extracts the acceptance criteria directly from the issue text to compare against code changes and tests.

What is the best way to audit code changes against issue requirements?

The best way to audit code changes against issue requirements is to generate a structured report with evidence by automatically extracting and classifying acceptance criteria from linked GitHub issues and comparing them to diffs and tests.

How do I classify GitHub issue requirements into Must Have and Nice to Have?

To classify GitHub issue requirements into Must Have, Should Have, and Nice to Have categories, use an automated QA parsing tool that extracts acceptance criteria from issue text and evaluates code changes against them.