メニュー
Git workflow guidance for commits, branches, and pull requests
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Interact with AgentOS Agent API endpoints. For standard operations (listing agents, running agents, streaming), use the provided CLI script first. Only write custom Python when the script cannot handle the use case (e.g., structured output, dependencies, cancellation, chaining multiple calls). Trigger when: running agents remotely, listing agents, creating agent tests, or asking things like "kick off a run in my test agent" or "what agents do I have configured?"
Interact with AgentOS Team API endpoints. For standard operations (listing teams, running teams, streaming), use the provided CLI script first. Only write custom Python when the script cannot handle the use case (e.g., cancellation, chaining multiple calls, custom error handling). Trigger when: running teams remotely, listing teams, creating team tests, or asking things like "what teams do I have configured?" or "run a task on my research team."
Interact with AgentOS Workflow API endpoints. For standard operations (listing workflows, running workflows, streaming), use the provided CLI script first. Only write custom Python when the script cannot handle the use case (e.g., custom event handling, chaining multiple workflow calls, error handling with retries). Trigger when: running workflows remotely, listing workflows, creating workflow tests, or asking things like "what workflows do I have?" or "run my content pipeline workflow."
Interact with AgentOS Traces API endpoints using the AgentOSClient SDK. For standard operations (listing traces, getting trace details, viewing stats), use the provided CLI script first. Only write custom Python when the script cannot handle the use case (e.g., debugging workflows that chain agent runs with trace inspection, custom filtering, or integration tests). Trigger when: importing AgentOSClient to work with traces, writing scripts to debug agent runs, creating trace tests, or asking things like "show me the traces from my last agent run" or "how many tokens did my agent use?"
Interact with AgentOS Evals API endpoints. For standard operations (listing evals, running accuracy/performance evals, getting eval details), use the provided CLI script first. Only write custom Python when the script cannot handle the use case (e.g., advanced filtering, update/delete operations, chaining evals, agent-as-judge). Trigger when: running evaluations, listing eval runs, benchmarking agents, or asking things like "run an accuracy eval on my agent" or "show me the latest eval results."
Interact with AgentOS Knowledge API endpoints. For standard operations (listing content, uploading files, searching, deleting), use the provided CLI script first. Only write custom Python when the script cannot handle the use case (e.g., pagination, updating metadata, bulk workflows, get config). Trigger when: uploading documents, searching the knowledge base, listing content, or asking things like "upload this md file to my knowledge base" or "search my docs for X."
| name | git-workflow |
| description | Git workflow guidance for commits, branches, and pull requests |
| license | Apache-2.0 |
| metadata | {"version":"1.0.0","author":"agno-team","tags":["git","version-control","workflow"]} |
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