Run any Skill in Manus with one click

constitution-check

Stars0

Forks0

UpdatedJune 12, 2026 at 15:08

Verify a change complies with the project's constitution and cost/privacy invariants before a PR. Use when reviewing a diff, before opening a PR, when the user asks "does this pass the constitution", "constitution check", or whenever a feature touches the project's high-risk invariants (the high-risk areas named in your profile's Invariant checklist, .claude/PROJECT.md).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Chris-Graffagnino

Chris-Graffagnino/creance

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	constitution-check
description	Verify a change complies with the project's constitution and cost/privacy invariants before a PR. Use when reviewing a diff, before opening a PR, when the user asks "does this pass the constitution", "constitution check", or whenever a feature touches the project's high-risk invariants (the high-risk areas named in your profile's Invariant checklist, .claude/PROJECT.md).

/constitution-check — Claude Code binding

The gate logic is runtime-neutral and lives in .claude/workflow/constitution-check.md — read that file now and execute it against the current diff (git diff main..HEAD).

It reads .claude/PROJECT.md (invariant checklist + boundaries) and the constitution that profile names. For maker≠checker independence, the same checklist is enforced by the constitution-auditor subagent (.claude/agents/) during the /next-task §7 gate; this skill is the inline self-check version.

More from this repository

same repository

next-task

Chris-Graffagnino/creance

Start the next unblocked task in the build with full ceremony (project specifics from the profile). Use when the user says "next task", "work the next task", "continue the build", "what's next", or names a task ID to implement. Picks the task, opens the issue, cuts the branch, implements with tests, verifies, and runs review — stopping at PR (review mode).

2026-07-110

pr-review

Chris-Graffagnino/creance

Verified review of an open PR — fetch the diff AND every inline reviewer comment (including bot/automated inline findings), verify each finding against current source (file:line) and run the project's checks where relevant, then post one structured, severity-ranked review comment. Never declares "no findings" until every inline comment is adjudicated and every finding is grounded to source. Project specifics from the profile. Use when the user says "review PR

2026-07-090

review-response

Chris-Graffagnino/creance

Resolve the reviewer findings on your own open PR end-to-end — fetch the diff AND every inline comment (human and bot/automated), verify each against current source (file:line), apply the minimum scoped fix with red→green proof, RE-RUN the §7 gate on the fix (maker ≠ checker — a fix is not self-certified), reply to every comment, and confirm the head is green. Never merges — stops for the owner. Pushes fixes and posts replies (the write posture pr-review lacks). Project specifics from the profile. Use when the user says "address the reviewer comments on PR

2026-07-090

intake

Chris-Graffagnino/creance

Convert owner-filed GitHub issues into the tasks-file backlog via PR (project specifics from the profile). Classifies each unmapped issue (no task ID in title, unreferenced by any live tasks file) into spec work / repo-maintenance / bug / duplicate / underspecified, screens it against the constitution, drafts the backlog entry on a branch, and lands it as a PR the owner ratifies by merging. Use when the user says "intake", "run intake", "convert issue

2026-07-070

triage

Chris-Graffagnino/creance

Morning read-only triage heartbeat for the build (project specifics from the profile). Reads the tasks file, git history, and GitHub issues/PRs, then writes a fresh state snapshot to the out-of-repo inbox. Surfaces the next unblocked task, stale checkboxes, open PRs needing review, blocked/owner items, and upcoming constitution risks. Use when the user says "triage", "morning triage", "what's the state of the build", or when fired on a schedule. NEVER edits code, opens issues/PRs, or commits.

2026-07-070

maker-eval

Chris-Graffagnino/creance

Run the standing maker-eval corpus (project specifics from .claude/PROJECT.md). Re-scores the MAKER — the generation path that writes the code — against the frozen golden-task corpus + per-task rubrics with the pinned judge, after a maker-behavior fingerprint change (the maker model resolution OR an instruction/runtime surface that shapes its output, not the model table alone) or on the weekly schedule. The maker analog of auditor-liveness for the reviewers. Executes each corpus task as a [headless run] of the maker, scores the output with a read-only [reviewer]-style judge, and APPENDS an observe-only record + transcript packet per task to the fenced eval channel — which never feeds a gate outcome, tier assignment, or gate semantics (P5). Use when the user says "maker eval", "run the maker corpus", "eval the maker", "re-score the maker", when triage flags MAKER-EVAL-STALE, or on the weekly schedule. Read-and-append only — never edits the frozen instrument, never gates, never merges.

2026-07-030

name	constitution-check
description	Verify a change complies with the project's constitution and cost/privacy invariants before a PR. Use when reviewing a diff, before opening a PR, when the user asks "does this pass the constitution", "constitution check", or whenever a feature touches the project's high-risk invariants (the high-risk areas named in your profile's Invariant checklist, .claude/PROJECT.md).

/constitution-check — Claude Code binding

The gate logic is runtime-neutral and lives in .claude/workflow/constitution-check.md — read that file now and execute it against the current diff (git diff main..HEAD).