Enable Proactive Git Commits After Task Phase Completion

[nblog]

🎯 Summary

This proposal suggests evolving the current "conservative feedback" approach in task-oriented agents to a more proactive automation model where agents automatically execute git commits after completing each implementation phase.

🔍 Context & Current Behavior

Currently, when agents (such as task/implementation-focused agents) complete a phase:

• ✅ They provide a suggested commit message to the user
• ✅ They report the phase as complete
• ❌ They wait for the user to manually stage and commit changes

A sensible baseline, but for those ready to level up: let the agent finish the job ⚡

💡 Proposed Enhancement

Introduce an option for agents to proactively execute git commits upon phase completion by leveraging the existing git-commit skill.

🚀 Benefits

Aspect	Current	Proposed
Automation Level	Manual commit required	Automatic commit on phase completion
Developer Flow	Interrupted at each phase	Continuous, unblocked flow
Commit Consistency	Depends on user discipline	Enforced Conventional Commits
Traceability	User-dependent	Each phase = 1 atomic commit

[WilliamBerryiii]

The maintainers are discussing this as a proposal right now. We will need a bit of time to consider the breadth of workflows we're trying to support, and the importance of human-in-the-loop for certain scales of implementation. There is some merit here for cloud agents and providing them specific commit points based on an implementation plan. But I will also say that for myself, I still prefer to set the commit points and drive them with intention. thinking this over