Validates the aiwf planning tree and explains every check finding code.
npx skills add https://github.com/23min/aiwf --skill aiwf-check-23min
Please help me install this Agent Skill. Skill: aiwf-check Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded/aiwf-check Command: npx skills add https://github.com/23min/aiwf --skill aiwf-check-23min
git push or a failed aiwf check run leaves you staring at cryptic finding codes like refs-resolve/unresolved or fsm-history-consistent/illegal-transition with no explanation of what went wrong or how to fix it. This Skill decodes every finding, tells you whether it blocks a push, and gives the remediation path. ## Core Features & Use Cases - Finding code reference: Explains every error and warning code emitted by aiwf check, from id collisions and broken references to FSM history violations and provenance audit failures. - Hook behavior guidance: Clarifies the difference between the fast pre-commit shape-only check and the full pre-push audit, including when each blocks and why. - Provenance audit scoping: Explains how --since <ref> controls the untrailered-commit audit range and what happens on branches with no upstream. - Use Case: Your push is rejected with ids-unique/trunk-collision. Ask the Skill what it means, and it explains that an id allocated on your branch collides with one on the trunk ref, and that aiwf reallocate is the fix. ## Quick Start Ask the assistant to explain why aiwf check reported a specific finding code and whether it blocks your push.High-intent search queries and answers about installing and using this skill.
Run `aiwf check` for a human-readable summary of findings, or `aiwf check --verbose` to expand every warning with its path, line, and remediation hint. Use `--format=json` for tooling integration.
The pre-push hook runs the full `aiwf check` and blocks on any error-severity finding, such as duplicate ids, unresolved references, illegal status transitions, or untrailered entity commits. Run `aiwf check` locally to see the exact finding code and its remediation hint.
It means an id allocated on your branch is also allocated on the configured trunk ref at a different path, so two different entities share it across branches. Resolve it with `aiwf reallocate` rather than a manual `git mv`, so references and history stay intact.
When the branch has no upstream, the untrailered-entity audit is skipped with a `provenance-untrailered-scope-undefined` warning. Pass `--since <ref>`, for example `aiwf check --since main`, or set an upstream with `git push -u origin <branch>`.
The pre-commit hook runs `aiwf check --shape-only`, a fast subset that only catches stray files under `work/`. The pre-push hook runs the full check covering frontmatter shape, references, FSM history, provenance, and contract config.
Entity bodies must cite real entity ids at canonical width; placeholder shapes like `<prefix>-NNNN` are rejected there, though they are fine in docs. Tokens inside backticks or code fences are exempt because they discuss id syntax rather than referencing an entity.
optiventAudit requirements and phase plans to create a categorized GAPS-PLAN.md.
mikeprasadAudit configuration files, plugin manifests, and knowledge repositories for drift and broken references.
CristoVenturesTrace file evolution and contributor activity from git history.
torrustRun unified Markdown, YAML, TOML, Rust, and shell script linters.