Menú
Git workflows for feature branches, merges, and PR creation with GitHub CLI. Use when asked to manage branches, sync with base, resolve conflicts, or create PRs.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Expo Router UI implementation guide. Use for Expo-specific components, navigation setup, native tabs, and implementation patterns.
Git commit workflow with conventional commits and staging hygiene. Use when asked to stage changes, write commit messages, or manage commits in multi-worktree setups.
Audit iOS accessibility for screens and flows. Use to check Dynamic Type, VoiceOver, touch targets, contrast, focus order, and reduced motion (platform guidance, not implementation).
Core iOS HIG guidance and design rules. Use when giving iOS UI/UX advice on layout, typography, color, spacing, controls, and iconography (not Expo Router implementation).
iOS motion and haptics guidance. Use when designing animations, transitions, or feedback states (platform guidance, not implementation).
Choose and review iOS navigation patterns (tabs, stacks, modals, sheets, deep links). Use when designing app structure or refactoring navigation (platform guidance, not implementation).
| name | git-pr-workflow |
| description | Git workflows for feature branches, merges, and PR creation with GitHub CLI. Use when asked to manage branches, sync with base, resolve conflicts, or create PRs. |
Standardize branch management and PR creation with GitHub CLI. Favor clear, minimal steps and ask for missing details (base branch, target repo, reviewers, labels) only when needed.
git checkout main
git pull origin main
git checkout -b feat/short-description
git push -u origin feat/short-description
git push
Rebase on the latest base branch to avoid conflicts:
git fetch origin
git rebase origin/main
If rebase is not desired, merge instead:
git fetch origin
git merge origin/main
git push -u origin feat/short-description
gh auth status
Basic PR:
gh pr create --title "type(scope): short description" --body "Detailed description"
Draft PR:
gh pr create --draft --title "wip: short description" --body "Work in progress"
With reviewers/labels/base:
gh pr create --base develop --title "fix(scope): short description" --body "Details" --reviewer @username --label bug,urgent
When asked to generate PR content, output raw markdown exactly using this template:
## Summary
[1-2 sentences: what changed and why]
## High-Level Changes
- [Change 1]: [user-facing or architectural impact]
- [Change 2]: [impact]
## Detailed Implementation
- [Component Architecture]: [new/changed components]
- [State Management & Logic]: [state/data/validation changes]
- [Dependencies]: [new/updated packages]
## Test Plan
- [ ] Manual test step 1
- [ ] Manual test step 2
- [ ] Automated tests pass
If working across multiple worktrees (e.g. ansel-agent-a, ansel-agent-b):
pwdgit status -sbgit rev-parse --show-toplevelgit worktree listgit -C /path/to/worktree ... if needed.git push -u origin <branch>git log main..HEADgit status -sbgh auth statusgh auth login