Stage and commit files associated with a specific Cash change.
npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-commit
Please help me install this Agent Skill. Skill: cash-commit Source: https://github.com/cashwu/Agentflow-SDD/tree/main/.agents/skills/cash-commit Command: npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-commit
This skill solves the challenge of managing multiple concurrent changes in a single repository by ensuring that only files relevant to a specific, tracked change are staged and committed, preventing accidental inclusion of unrelated work.
Ask the assistant to commit the files associated with your current active change name.
High-intent search queries and answers about installing and using this skill.
Precision-staged commits filter dirty files against tracked Cash change state to stage only source and artifact files relevant to a specific change. This prevents accidental inclusion of unrelated work when managing multiple concurrent updates in a single repository.
Intent-based staging is automated by validating change tracking through the local Cash CLI to ensure atomic commits. The system resolves shared review-loop signals and filters dirty files to stage only the specific source and artifact files associated with your active change.
Yes, the local Cash CLI is required to validate change tracking and ensure atomic, intent-based staging. Both Git and the Cash CLI are necessary dependencies to filter dirty files and manage granular commits across complex workflows.
Yes, archive integration seamlessly handles post-archive states to allow commits even after a change has been archived. This ensures spec synchronization and shared review-loop signal resolution remain functional throughout the change lifecycle.
Unrelated files are staged without change-aware filtering because dirty files are not being filtered against tracked Cash change state. To prevent accidental inclusion, use precision-staged commits to validate change tracking and isolate source and artifact files for your specific change.
Yes, spec synchronization and shared review-loop signal resolution are supported as part of complex workflow management. The system validates change tracking to ensure atomic, intent-based staging of source and artifact files during these operations.
zrongFormat git commit messages, stage atomic changes, and generate CalVer tags.
autorundevAutomate git commit and push with a predefined message template.
semicolon-devteamAutomate SEMO package semantic versioning with VERSION updates and Keep a Changelog compliance.
chanhee-kangSplit and reorder Git commits into atomic changes with safe rebasing.
