checkin

Runs pre-commit quality gates over staged changes and produces a unified pass/fail verdict.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill checkin-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkin
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/checkin
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill checkin-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before every commit, developers must manually run code review, ICEA compliance checks, secrets scanning, and security findings checks — a slow, error-prone sequence that is easy to skip. This Skill consolidates all of those gates into a single pre-commit pass over staged and modified files, returning one clear verdict and a ready-to-use commit command. ## Core Features & Use Cases - Unified multi-check gate: Runs static code analysis (Check A), ICEA compliance via the pr-spec-review engine (Check B), secrets and sensitive-file scanning (Check C), business-context severity escalation (Check 5b), and the open Critical/High security findings gate (Check D) in one pass. - Hard blocking rules: Blocks the commit on Critical/High findings, missing acceptance criteria, detected secrets, or open Critical/High security ledger findings; warnings never block. - Traceability instrumentation: Computes change-manifest precision/recall against the ICEA and detects D-option drift, appending accuracy metrics without blocking the commit. - Use Case: A developer on branch ADO-1234 stages changes and invokes the gate; the Skill reports PASS on all checks and emits a pre-filled git commit -m "[ADO-1234] ..." command. ## Quick Start Run the checkin gate on my staged changes and tell me whether it is safe to commit.

Frequently Asked Questions about checkin

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

FAQPage Schema
How do I run pre-commit checks on staged git changes?

Invoke the checkin gate after staging files with git add. It runs code quality analysis, ICEA compliance, secrets scanning, and the security findings gate in one pass, then outputs a unified pass/fail verdict with a suggested commit command.

What checks does a pre-commit quality gate include?

This gate includes static code analysis on changed files, ICEA acceptance-criteria compliance, secrets and sensitive-file detection, business-context severity escalation, and a check for open Critical/High findings across code-review, security, and DAST ledgers.

Can the secrets scan be skipped before committing?

No. The secrets check is a hard gate that always runs and cannot be skipped with any flag. The security findings gate can only be bypassed with --skip-security-gate plus a written justification recorded in the commit message.

What happens when a commit is blocked by the gate?

The verdict shows BLOCKED and lists each blocking issue with its file, line, and a one-line fix. No commit command is emitted. Blocks occur on Critical/High findings, missing acceptance criteria, detected secrets, or open Critical/High ledger findings.

Does the pre-commit gate work without an ICEA file?

Yes, but the ICEA compliance check reports SKIPPED and the other checks still run normally. You are advised to run the ICEA review separately once the ICEA file for the current ADO item is located.