git-status
Present the status of the git repository to the user. Use to display the status of the repository after a successful git commit by the agent. The agent should not use this internally for its own needs.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Present git status
GOAL: present the git status in a visually appealing and
consistent way.
WHEN: use after a successful git commit by the agent when it needs
to display the status of the repository to the user.
NOTE: The agent shouldn't use this internally for its own needs.
Efficiency directives
- Optimize all operations for token and context efficiency
- Batch operations on file groups, avoid individual file processing
- Use parallel execution when possible
- Target only relevant files
- Reduce token usage
Git directives
For repository status
git status --porcelain=v2 --branch
References
The following reference files serve as strict guidelines:
-
references/git-status-codes.md: complete reference for parsing git status output -
references/git-status-presentation.md: git status presentation guidelines, examples, and templates
Workflow
IMPORTANT: To avoid a recursive loop, DON'T invoke the
git-status skill here.
- Without using the
git-statusskill, get repository status - Use the reference files templates to present final status to user
-
DONE
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-31
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!