一键在 Manus 中运行任何 Skill

commit-readiness

星标2

分支0

更新时间2026年6月27日 13:58

Verify hooks ran, no secrets, protected paths untouched, and commit message valid before committing. Owned by the reviewer.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

mahmoud-emad-dev

mahmoud-emad-dev/aspis

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

commit-readiness

Purpose

Before any commit lands, confirm the git hooks fired correctly, no secrets leaked into the diff, no protected path was touched without R-008 approval, and the commit message follows the project convention. This is the last deterministic gate before the committer writes — the reviewer owns it, the committer consults it.

When to use

Before every commit — invoked by the committer or the reviewer in the pre-commit review path.
When a hook reports a warning but the committer is unsure whether to proceed.
After a scope-compliance check flags protected paths — re-verify here.

Procedure

Hooks ran — confirm pre-commit and commit-msg hooks executed without block. A skipped hook (.git/hooks/pre-commit missing or non-executable) is a HIGH finding — refuse the commit.
No secrets — scan the staged diff (git diff --cached) for secret patterns (keys, tokens, passwords). Any hit is CRITICAL — refuse the commit.
Protected paths — cross-check every changed file against the protected path set (R-008, .aspis/state/approval-ledger.yaml). A protected path without an active governance approve entry is CRITICAL — refuse the commit.
Valid message — the commit message must match the convention (type(scope): description ≤72 chars). Non-conforming messages are MEDIUM — block unless the committer provides an explicit reason.
All clear — emit COMMIT-READY only when every gate passes. Any finding that blocks returns COMMIT-BLOCKED with file:line evidence per the finding-format skill.

Outputs

Verdict: COMMIT-READY or COMMIT-BLOCKED.
Per-finding details with severity, location, and evidence (finding-format).
Hook execution summary (pre-commit / commit-msg / post-commit status).

Anti-patterns

Skipping the hooks check because "they always pass" — a disabled hook is silent drift and the first sign of a broken gate.
Allowing a commit with a protected-path touch because "it's just a doc fix." Protected means protected — R-008 approval is the only path.
Accepting a non-conforming commit message with a vague promise to fix it later — the message is the permanent audit trail.

同仓库更多 Skills

同仓库

commit-splitting

mahmoud-emad-dev/aspis

Keep commits atomic — split a mixed change set into scoped, reviewable commits.

2026-07-012

project-onboarding

mahmoud-emad-dev/aspis

The one-time procedure to take an exported project to live — understand it, confirm the name/goal/stack with the user, run the deterministic `aspis bootstrap`, enrich the judgment files (AGENTS.md, ARCHITECTURE, context), verify, and let the package self-clean. Followed by the bootstrap agent.

2026-06-292

architecture-memory

mahmoud-emad-dev/aspis

Keep per-subsystem architectural intent current through the planning loop — read before designing, record an impact report on change, confirm with the user, apply a dated update, and verify the build against approved intent.

2026-06-292

dependency-audit

mahmoud-emad-dev/aspis

Audit a plan's task dependency graph for structural integrity — circular dependencies, missing prerequisites, orphan tasks, and dependency classification (hard/soft/warning). Produces a pass/warn/fail audit report per dependency so planners catch graph errors before build starts.

2026-06-272

clean-tree-precondition

mahmoud-emad-dev/aspis

Every editing agent should start on a clean working tree so parallel work never collides.

2026-06-272

byte-parity-checker

mahmoud-emad-dev/aspis

Prove the catalog regenerates the live runtime byte-for-byte; refuse export on any mismatch.

2026-06-272

commit-readiness

Purpose

When to use

Before every commit — invoked by the committer or the reviewer in the pre-commit review path.

When a hook reports a warning but the committer is unsure whether to proceed.

After a scope-compliance check flags protected paths — re-verify here.

Procedure

Hooks ran — confirm pre-commit and commit-msg hooks executed without block. A skipped hook (.git/hooks/pre-commit missing or non-executable) is a HIGH finding — refuse the commit.

No secrets — scan the staged diff (git diff --cached) for secret patterns (keys, tokens, passwords). Any hit is CRITICAL — refuse the commit.

Protected paths — cross-check every changed file against the protected path set (R-008, .aspis/state/approval-ledger.yaml). A protected path without an active governance approve entry is CRITICAL — refuse the commit.

Valid message — the commit message must match the convention (type(scope): description ≤72 chars). Non-conforming messages are MEDIUM — block unless the committer provides an explicit reason.

All clear — emit COMMIT-READY only when every gate passes. Any finding that blocks returns COMMIT-BLOCKED with file:line evidence per the finding-format skill.

Outputs

Verdict: COMMIT-READY or COMMIT-BLOCKED.

Per-finding details with severity, location, and evidence (finding-format).

Hook execution summary (pre-commit / commit-msg / post-commit status).

Anti-patterns

Skipping the hooks check because "they always pass" — a disabled hook is silent drift and the first sign of a broken gate.

Allowing a commit with a protected-path touch because "it's just a doc fix." Protected means protected — R-008 approval is the only path.

Accepting a non-conforming commit message with a vague promise to fix it later — the message is the permanent audit trail.

name	commit-readiness
description	Verify hooks ran, no secrets, protected paths untouched, and commit message valid before committing. Owned by the reviewer.