signoff

Verifies human comprehension of branch diffs via Socratic interview and records Git attestation trailers.

9|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/jerrylin96/dotgemini --skill signoff-jerrylin96
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signoff
Source: https://github.com/jerrylin96/dotgemini/tree/main/skills/signoff
Command: npx skills add https://github.com/jerrylin96/dotgemini --skill signoff-jerrylin96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code diffs are often merged after rubber-stamp review, leaving no record that a human actually understood the change or accepted its risks. This Skill runs a structured Socratic reverse-interview before merge and records the outcome as a machine-parsable Git attestation, creating accountability and an audit trail. ## Core Features & Use Cases - Socratic Comprehension Interview: Probes four fixed axes (mechanics, trade-offs, failure loudness, ownership) at cursory, standard, or skeptical intensity, with automatic escalation for large or scientific diffs. - Git Signoff Attestation (GSA) Protocol: Writes flat trailers into an empty signed commit and mirrors them to refs/notes/signoff so attestations survive squash merges and branch deletion, with transcript SHA256 digests for later re-verification. - Harness-Agnostic Portability: Ships adapters for Antigravity CLI, Claude Code (web and CLI), Codex CLI, and a generic file override, plus swappable interview profiles (software-general, domain-science) resolvable per repository. - Use Case: Before merging a feature branch that modifies a numerical solver, run /signoff --deep; the agent challenges you to predict behavior on edge inputs, then commits a signed attestation recording the reviewed commit SHA, tree SHA, transcript digest, and acknowledged risks. ## Quick Start Ask the agent to run /signoff on your current feature branch before merging it into main.

Frequently Asked Questions about signoff

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

FAQPage Schema
How do I sign off on a branch before merging with AI-generated code?▼

Run /signoff on the feature branch. The agent inspects the range diff, interviews you on mechanics, trade-offs, failure modes, and ownership, then creates an empty attestation commit with GSA trailers and mirrors it to refs/notes/signoff.

What is the Git Signoff Attestation (GSA) protocol?▼

GSA is an open specification for recording human code attestation as flat Git trailers in an empty commit plus Git notes. It captures reviewed commit and tree SHAs, a transcript SHA256 digest, acknowledged risks, and the verifier's email.

Does the signoff skill work with Claude Code and Codex CLI?▼

Yes, it ships transcript adapters for Antigravity CLI, Claude Code web and CLI, and Codex CLI, plus a generic SIGNOFF_TRANSCRIPT_FILE override for other harnesses. Adapter resolution follows a fixed env-var precedence order.

What happens if the session transcript is unavailable during signoff?▼

The attestation is downgraded to VERIFIED_BY_HUMAN_NO_TRANSCRIPT_DIGEST with digest fields set to unavailable. This status requires a second explicit user confirmation and a repeated clean-state check before the commit proceeds.

Can I customize the interview questions for scientific or research code?▼

Yes, place a profile file at .signoff/profile.md in the target repository or set SIGNOFF_PROFILE_FILE. Profiles add domain emphases within the fixed axes but cannot remove axes or lower pass criteria; a science-detection guard also escalates automatically.

Do signoff attestations survive squash merges and branch deletion?▼

Yes, the attestation payload is mirrored into refs/notes/signoff attached to both the reviewed commit SHA and its tree SHA. Verifiers look up notes first, then fall back to git log and tree-SHA matching.