Commits markdown body edits to aiwf planning entities through a trailered verb route.
npx skills add https://github.com/23min/aiwf --skill aiwf-edit-body-23min
Please help me install this Agent Skill. Skill: aiwf-edit-body Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded/aiwf-edit-body Command: npx skills add https://github.com/23min/aiwf --skill aiwf-edit-body-23min
git commit bypasses the framework's provenance trailers and triggers a provenance-untrailered-entity-commit warning. This Skill routes body edits through the aiwf edit-body verb so every change lands as a properly trailered commit. ## Core Features & Use Cases - Bless mode: Edit the entity file in your editor, review the diff, then run aiwf edit-body <id> to commit exactly what was reviewed. - Explicit-content mode: Supply body content via --body-file <path> or stdin when an LLM session, script, or pipeline produces the text without an editor round-trip. - Guardrails: Refuses empty diffs, frontmatter changes, new entities without a HEAD version, and removal of required ## Section headings, pointing to the correct verb (aiwf add, aiwf promote, aiwf rename, aiwf cancel) instead. - Use Case: After a review round, rewrite the rationale section of ADR-0003 in your editor, then run aiwf edit-body ADR-0003 --reason "incorporate review feedback" to record the change with full provenance. ## Quick Start Ask the assistant to update the body prose of entity M-0002 using aiwf edit-body so the change is committed with proper trailers.High-intent search queries and answers about installing and using this skill.
Edit the entity's markdown file in your editor, then run `aiwf edit-body <id>` to commit the working-copy changes in one trailered commit. This bless mode avoids the `provenance-untrailered-entity-commit` warning a plain git commit would trigger.
Edit the prose under the `### AC-N — title` heading in the parent milestone file, then run `aiwf edit-body M-NNNN`. Composite ids like M-NNNN/AC-N are refused; bless mode on the parent milestone covers the workflow.
No. Both modes are body-only and refuse when the working copy's frontmatter differs from the committed version. Use `aiwf promote`, `aiwf rename`, `aiwf cancel`, or `aiwf reallocate` for structured-state changes.
Bless mode refuses when the working copy matches the committed version, since it cannot distinguish an intentional no-op from an unsaved editor buffer. Explicit `--body-file` mode instead reports 'nothing to commit' at exit 0 when the target content is already in place.
Use `--body-file <path>` or stdin when body content is produced outside the working copy, such as by an LLM session, script, or pipeline. For interactive edits a human will review, bless mode is preferred because the diff is reviewable before commit.
CommandCodeAIScaffold new Skills with standardized frontmatter and body structure.
Alpizar28Define and validate deterministic state machine lifecycles for reservation entities.
jacazul-aiEnforce conventional commit prefixes, body reasoning, and ticket references in Git commits.
MolcajeteAIGenerate Git commit messages from staged changes and project history.