pr-workflow
Pull Request Workflow
Complete workflow for creating pull requests following project standards.
Process
-
Verify staged changes exist with
git diff --cached --name-only -
Branch setup
- If on main/master, create feature branch first:
feature/brief-descriptionorfix/brief-description - Use
github-dev:commit-creatorsubagent to handle staged changes if needed
- If on main/master, create feature branch first:
-
Documentation check
- Update README.md or docs based on changes compared to target branch
- For config/API changes, use
mcp__tavily__tavily_searchto verify info and include sources
-
Analyze all commits
- Use
git diff <base-branch>...HEADto review complete changeset - PR message must describe all commits, not just latest
- Focus on what changed from reviewer perspective
- Use
-
Create PR
- Use
/pr-creatoragent orgh pr createwith parameters:-t(title): Start with capital letter, use verb, NO "fix:" or "feat:" prefix-b(body): Brief summary + bullet points with inline markdown links-a @me(self-assign)-r <reviewer>: Only add if the user explicitly asks OR recent PRs by this author have reviewers. Check with:gh pr list --repo <owner>/<repo> --author @me --limit 5 --json reviewRequestsIf recent PRs have no reviewers, skip-rentirely.
- Use
-
PR Body Guidelines
- Single section, no headers if possible. Very concise
- Few bullet points + 1 CLI/usage snippet or simple before/after snippet
- No test plans, no changed file lists, no line-number links
Examples
CLI snippet:
Add compare command for side-by-side model comparison
- Run multiple models on same images with `--models` and `--phrases` flags
- Horizontal panel concatenation with model name headers
`ultrannotate compare --source ./images --models sam3.pt,yoloe-26x-seg.pt --phrases "person,car"`
Before/after:
Inline single-use variables in compare_models
- xyxy2xywhn handles empty arrays, guard unnecessary
- Use function reference for draw dispatch
Before: `boxes = result.get(...); ops.xyxy2xywhn(boxes, ...)`
After: `ops.xyxy2xywhn(result.get(...), ...)`
More from fcakyon/claude-codex-settings
paper-search-usage
This skill should be used when user asks to "search for papers", "find research papers", "search arXiv", "search PubMed", "find academic papers", "search IEEE", "search Scopus", or "look up scientific literature".
91gcloud-usage
This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".
62setup
This skill should be used when the user asks "how to setup GitHub CLI", "configure gh", "gh auth not working", "GitHub CLI connection failed", "gh CLI error", or needs help with GitHub authentication.
53tavily-usage
This skill should be used when user asks to "search the web", "fetch content from URL", "extract page content", "use Tavily search", "scrape this website", "get information from this link", or "web search for X".
48azure-usage
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
48mongodb-usage
This skill should be used when user asks to "query MongoDB", "show database collections", "get collection schema", "list MongoDB databases", "search records in MongoDB", or "check database indexes".
47