finalize-minor-task

To organize small git changes into a structured commit, analyze the git status and diff to categorize the changes, generate a MinorTasks archive with a plan.md, create a changelog fragment, and format a git commit message.

Archiving minor bug fixes and configuration updates without a full feature workflow involves creating a MinorTasks archive folder, documenting the change intent in a plan.md, and generating a changelog fragment before committing.

Yes, you can generate a changelog fragment and commit message from a git diff for UI edits by analyzing the changed files, determining the modification type, and applying a properly formatted commit prefix to stage and commit the files.

This minor task archiving process works for balance tweaks and small maintenance tasks by treating them as MinorTasks, creating dedicated archive entries, and producing structured changelog fragments instead of following the feature implementation process.

Formatting git commit messages for small maintenance tasks without a specification requires analyzing the git diff, determining the correct commit prefix based on the change type, and staging files individually before executing the commit.

You should not use a minor task archiving workflow for code changes when the modifications follow the feature implementation process, as this workflow is specifically designed for bug fixes, UI edits, and configuration updates that lack formal specifications.