check-premises

Verify claims about code against the repository before building on them.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/serhii-baksheiev/create-agent-rig --skill check-premises-serhii-baksheiev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-premises
Source: https://github.com/serhii-baksheiev/create-agent-rig/tree/main/.agents/skills/check-premises
Command: npx skills add https://github.com/serhii-baksheiev/create-agent-rig --skill check-premises-serhii-baksheiev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Queue items and PR prose assert things about the code that may be false, and downstream review never re-checks them because the diff and the item are wrong in the same direction. This skill catches false premises before work is built on them, preventing duplicate implementations, fixes in the wrong file, and unbacked behaviour claims in shipped documentation. ## Core Features & Use Cases - Pre-work premise verification: Extracts the load-bearing claims from a queue item and checks each against the actual code with file:line citations, returning PREMISES HOLD, PREMISE FALSE, or UNVERIFIABLE. - Pre-gate prose audit: A second entry point checks the run's own rulebook prose and PR description for behaviour claims nothing backs, returning UNMEASURED with exactly two exits: delete the sentence or point it at the test that proves it. - Structured verdict block: Emits a single fenced JSON verdict with blockers, evidence, and the head SHA of the tree examined, so the calling loop can validate the report mechanically. - Use Case: A queue item says "the schema does not reject an empty title". The skill reads the validator, finds it does reject empty titles, and reports PREMISE FALSE with the citation — the task becomes a caller fix instead of a duplicate validation rule. ## Quick Start Ask the agent to check the premises of this queue item against the code before starting the failing test.

Frequently Asked Questions about check-premises

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

FAQPage Schema
How do I verify a task's assumptions before writing code?

List the claims the task makes about the code as it exists now, mark the load-bearing ones whose falsity would change what gets built, and read the actual code to confirm or contradict each with a file:line citation. Skip claims a failing test would expose immediately.

What is a false premise in a coding task?

A false premise is a claim in a queue item that the code contradicts, such as "there is no validation on that field" when validation already exists. Building on it produces correct, tested, reviewed work that solves a problem that does not exist.

When should premise checking run in a TDD workflow?

Run it after selecting a queue item and before the Red step, so false premises stop the work before a test is written. Run it again before the review gate on your own prose, where an unbacked behaviour claim is reported as UNMEASURED.

What does an UNMEASURED verdict mean?

UNMEASURED means a sentence you wrote asserts behaviour and nothing you can point at backs it. It has exactly two exits: delete the sentence, or turn it into a pointer naming the test that proves the claim.

What are the limitations of checking premises against code?

It only catches what the code can contradict. Claims about runtime behaviour, intent, or systems outside the repository are UNVERIFIABLE rather than false, and the verdict is a self-report with no hook enforcing that the check ran.