check

Verify recent git changes against a specific question using read-only evidence.

5|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Nathan13888/nice-skills --skill check-nathan13888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/Nathan13888/nice-skills/tree/main/skills/check
Command: npx skills add https://github.com/Nathan13888/nice-skills --skill check-nathan13888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers and code-reviewing agents quickly verify whether a specific expectation about recent work is true by collecting git and codebase evidence and producing a concise, verdict-first response.

Core Features & Use Cases

  • Verdict-first answers: Produces a clear YES / NO / PARTIAL or concise explanation up front for senior readers.
  • Read-only evidence gathering: Aggregates git status, unstaged and staged diffs, recent commits, and targeted file reads without modifying files.
  • Conditional depth: Runs tests or spawns a Task agent for complex, multi-file investigations and clarifies ambiguous or out-of-repo queries.

Quick Start

Ask the agent: /check does the new endpoint handle errors?

Frequently Asked Questions about check

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

FAQPage Schema
How do I verify recent git changes against a specific code review question?

Yes, you can verify if code changes handle specific behavior by analyzing git diffs and recent commits. The Skill aggregates staged and unstaged changes alongside codebase context, running selective tests to output a clear YES, NO, or PARTIAL verdict.

How does evidence-backed verification work for local repositories?

You can verify endpoint behavior by asking the agent to check if the new endpoint handles errors. The Skill gathers git diffs, recent commits, and codebase context, generating a verdict-first response confirming whether the expected behavior is true.

Can I run tests during a code review session without modifying files?

Yes, you can run tests for verification without modifying files. The Skill performs read-only evidence collection and conditionally runs selective tests or spawns a Task agent for complex multi-file investigations to confirm code changes.

Does this code review verification tool work with out-of-repo queries?

For ambiguous or out-of-repo queries, the verification tool clarifies the request rather than guessing. It focuses on collecting local git repository evidence from recent commits and diffs to produce a concise verdict-first report.

What is the best way to confirm recent edits match expected behavior in git?

The best way to confirm recent edits match expected behavior is through verdict-first verification. The Skill analyzes git status, unstaged diffs, and targeted file reads to deliver a concise YES, NO, or PARTIAL explanation up front for senior readers.

Are there limitations when verifying staged and unstaged changes?

The main limitation is that the Skill performs only read-only evidence collection and applies strictly to local git repositories. It clarifies ambiguous or out-of-repo queries rather than modifying files or executing comprehensive test suites.