Change Mapper

To make atomic commits with documentation references, the Skill scans git status, groups modified files into logical changesets, locates matching markdown references, and executes policy-compliant commits. This verifies each changeset before committing.

An atomic commit groups a single logical change, like a UI theme update, strictly tied to a documentation reference. You need it to prevent disorganized commits and keep project history cleanly mapped to specific feature updates or track files.

To separate mixed staged changes into logical git commits, the Skill categorizes modified files into distinct changesets based on feature or task. It then drafts specific commit messages for each group, ensuring mixed API and UI updates are committed separately.

Yes, you can verify git diffs and draft commit messages according to policy automatically. The Skill performs a fact check on your staged diffs and generates policy-adhering commit messages before executing the final atomic commits.

Yes, this works with application documentation and track files for commit verification. The Skill hunts for relevant markdown references in your application_documentation or conductor/tracks directories to verify changesets before committing.