Automated Accounting
The AI handles the cognitive gear-shift of writing descriptive commit messages and Pull Request (PR) descriptions. Why this matters: Your brain is in “implementation mode”—switching to “documentation mode” is expensive.Writing Commit Messages
Ask the AI to generate commit messages based on the chat history.Example Prompt
What Good Commit Messages Look Like
Bad:Automated Message Generation
For work done in a single chat session:Contextual Commits
For work spanning multiple sessions, ensure the AI has full context.The Problem
AI only sees the current chat—it doesn’t know about earlier sessions.The Solution
Prompt the AI to rungit diff to see all changes:
What This Prevents
- Incomplete commit messages
- Missing context from earlier work
- Commits that don’t reflect full scope
Writing PR Descriptions
Generate comprehensive PR descriptions from the full context.PR Description Template
Example Prompt
Using GitHub CLI (gh)
Leverage the AI to interact with gh (GitHub CLI) for automated workflows.
Creating PRs Automatically
What the AI Generates
Agentic Mechanics
Use AI to automate the “boring” parts of the finish line:Automate These Tasks
- ✅ Write commit messages
- ✅ Generate PR descriptions
- ✅ Update changelogs
- ✅ Create release notes
- ✅ Update documentation
- ✅ Run final checks (tests, linting)
Keep Human Control Over
- ❌ Merging to main/master
- ❌ Production deployments
- ❌ Breaking changes
- ❌ Security-sensitive operations
Pre-Ship Checklist
Before shipping, verify:- All tests pass locally
- Linting passes
- Type checking passes
- No debug statements or console.logs
- Git diff reviewed manually
- Commit message is descriptive
- PR description is comprehensive
- Breaking changes are documented
- CI/CD pipeline will pass
The Final Push
Standard Workflow
Key Principle: AI handles documentation overhead. You maintain control over delivery decisions. Automate the boring, control the critical.