Get practical guidance for Git commits, branch names, and pull requests. The skill follows a consistent commit format, offers naming patterns and a PR description template, and includes common commands for starting, updating, and submitting work.
Git workflow guidance for commits, branches, and pull requests
Run score Not tested
See how to installThe git-workflow skill helps with Git commits, branch names, and pull requests. It provides a commit message format with a type, scope, subject, body, and related ticket, along with examples for features and fixes. For branches, it shows a naming pattern that combines the work type, ticket ID, and a short description. For pull requests, it offers a template covering the summary, changes, testing, and checklist.
The skill also lists common Git commands for starting work, staging changes, updating a branch, and creating a pull request. For generating and checking commit messages, it instructs the agent to use the included commit_message.py script.
Use it when you want consistent commit and branch names across a team, need to decide what to include in a pull request, or want to refer to a basic Git workflow while working.
The skill is licensed under Apache-2.0. Its instructions call for using commit_message.py to generate and validate commit messages.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 25, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
You are a Git workflow assistant. Help users with commits, branches, and pull requests following best practices.
For commit message generation and validation, use get_skill_script("git-workflow", "commit_message.py").
<type>(<scope>): <subject>
<body>
<footer>
feat(auth): add OAuth2 login support
Implemented OAuth2 authentication flow with Google and GitHub providers.
Added token refresh mechanism and session management.
Closes #123
fix(api): handle null response from external service
Added null check before processing response data to prevent
NullPointerException when external service returns empty response.
Fixes #456
<type>/<ticket-id>-<short-description>
feature/AUTH-123-oauth-loginfix/BUG-456-null-pointerchore/TECH-789-update-depsFollow commit message format for the title.
## Summary
Brief description of what this PR does.
## Changes
- Change 1
- Change 2
## Testing
How was this tested?
## Checklist
- [ ] Tests added/updated
- [ ] Documentation updated
- [ ] No breaking changes
git checkout main
git pull origin main
git checkout -b feature/TICKET-123-description
git add -p # Interactive staging
git commit -m "type(scope): description"
git fetch origin
git rebase origin/main
git push -u origin feature/TICKET-123-description
# Then create PR on GitHub/GitLab
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Reviews code for style, naming, error handling, exposed credentials, and possible bugs, security, or performance issues. It can run an automated style check and returns structured feedback grouped by severity, from critical fixes to optional improvements.
Reviews configured sources and proposes actionable backlog tasks tied to a suitable project. Each proposal cites inspected evidence and its observed content hash, while stable keys prevent duplicate proposals across later scans.
Refreshes a product’s status using its playbook, projects, tasks, and configured sources. It records observed progress and failures, removes references to archived work, and presents project completion proposals for human review without changing task or project states.
Summarizes a Product’s recorded changes, pending owner actions, and failures since the last successful delivery. It writes the report to the configured wiki and sends it through the configured interface, or records a quiet check when nothing needs attention.
Inspect the host running the AgentOS process, including its operating system, architecture, Python runtime, processor, and UTC time. You can also list the direct contents of a chosen directory, with the skill folder as the default location.