commit
- Repo stars 846
- Author repo modbus
- Domain
- Engineering
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @digitalpetri · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
You are tasked with creating git commits for the changes made during this session.
## Process
1. **Think about what changed:**
- Review the conversation history and understand what was achieved
- Run `git status` to see current changes
- Run `git diff` to understand the modifications
- Consider whether changes should be one commit or multiple logical commits
2. **Plan your commit(s):**
- Identify which files belong together
- Draft clear, descriptive commit messages
- Use imperative mood in commit messages
- Focus on why the changes were made, not just what
3. **Present your plan to the user:**
- List the files you plan to add for each commit
- Show the commit message(s) you'll use
- Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"
4. **Execute upon confirmation:**
- Use `git add` with specific files (never use `-A` or `.`)
- Create commits with your planned messages
- Show the result with `git log --oneline -n [number]`
## Remember
- You have the full context of what was done in this session
- Group related changes together
- Keep commits focused and atomic when possible
- The user trusts your judgment – they asked you to commit
- Write commit messages as if the user wrote them
Sections and files
Listed in source order.
sections -> Process → Remember
terms -> Think about what changed · Plan your commit(s) · Present your plan to the user · Execute upon confirmation
files/cmd -> git status · git diff · git add · git log --oneline -n [number]
body sha256 -> 55cf12ca2fd3
Process
Think about what changed: Review the conversation history and understand what was achieved Run
git statusto see current changes Rungit diffto understand the modifications Consider whether changes should be one commit or multiple logical commitsRemember
You have the full context of what was done in this session Group related changes together Keep commits focused and atomic when possible The user trusts your judgment – they asked you to commit Write commit messages as if the user wrote them