aiwf-acknowledge

Records human-authored git commit exemptions for aiwf audit findings with written rationale.

Updated May 9, 2026
One-click install
npx skills add https://github.com/23min/aiwf --skill aiwf-acknowledge-23min
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwf-acknowledge
Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded/aiwf-acknowledge
Command: npx skills add https://github.com/23min/aiwf --skill aiwf-acknowledge-23min

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When aiwf check flags a finding you have judged to be intentional — a historical commit with an illegal FSM transition that cannot be rewritten, or an area-mistag warning on genuinely cross-cutting work — you need a sovereign, auditable way to exempt it without polluting config files or rewriting shared history. ## Core Features & Use Cases - Exempt historical commits: aiwf acknowledge illegal <sha> records an empty commit with aiwf-verb / aiwf-actor / aiwf-reason trailers that exempts the named SHA from the fsm-history-consistent and provenance audit rules. - Accept cross-cutting mistags: aiwf acknowledge mistag <id> suppresses the area-mistag warning for an entity whose work legitimately spans areas. - Sovereign-act enforcement: Both subverbs refuse non-human/ actors and empty --reason values, so every exemption traces to a named human with written rationale, queryable via aiwf history. - Use Case: A pre-rule squash-merge collapses intermediate FSM steps and blocks your pre-push hook with an illegal-transition error. Run aiwf acknowledge illegal <sha> --reason "..." to record the exemption as a git-native audit entry. ## Quick Start Ask the AI to run aiwf acknowledge illegal with the offending commit SHA and a written reason to exempt it from the FSM history audit.

Frequently Asked Questions about aiwf-acknowledge

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

FAQPage Schema
How do I exempt a historical commit from aiwf FSM history checks?

Run aiwf acknowledge illegal <sha> --reason "..." to record an empty commit with aiwf-verb, aiwf-actor, and aiwf-reason trailers. Check rules walk HEAD's reachable history for these trailers and exempt the named SHA from fsm-history-consistent and provenance audit findings.

How do I suppress an area-mistag warning in aiwf?

Run aiwf acknowledge mistag <id> --reason "..." when the cross-cutting work is intentional. If the area tag is simply wrong, use aiwf set-area instead, which stops the warning from firing without needing an acknowledgement.

When should I not use aiwf acknowledge illegal?

Do not use it for fresh, fixable transitions — re-route through aiwf promote or aiwf cancel, or use --force --reason at change time. Untrailered but FSM-legal edits are the manual-edit subcode, cleared via --audit-only, not an acknowledge.

Can an aiwf acknowledgement be reversed or undone?

No, acknowledgements are one-way by deliberate design with no un-acknowledge verb. To undo a mistag ack, re-tag with aiwf set-area so the finding no longer fires; an illegal ack is lived with or rewritten out of history.

Why does aiwf acknowledge reject my actor or empty reason?

Both subverbs require a human/... actor and a non-empty --reason because acknowledgements are sovereign acts that must trace to a named human with written rationale. The verb also rejects SHAs not reachable from HEAD or the object database and ids resolving to no entity.