configs/commands/skills/commit-push-pr/SKILL.md
Complete workflow to commit changes, push to remote, and create a pull request. Use when you want to ship changes end-to-end in one operation, from local changes to an open PR.
npx skillsauth add heyayushh/stacc commit-push-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
One-shot workflow for committing, pushing, and creating a pull request.
origin is configuredgh) is installedCheck branch
BRANCH=$(git branch --show-current)
if [ "$BRANCH" = "main" ] || [ "$BRANCH" = "master" ]; then
echo "Direct pushes to main/master not allowed"
exit 1
fi
Stage and commit
git add -A
git commit -m "<prefix>: <summary>"
Push
git push -u origin "$BRANCH"
Create PR
gh pr create --title "<prefix>: <summary>" --body "$(cat <<'EOF'
## Summary
- Change description
## Test plan
- How to verify
EOF
)"
When generating PR content, use:
git branch --show-current # Branch name for intent
git merge-base origin/main HEAD # Merge base
git diff --name-status $(git merge-base origin/main HEAD)...HEAD # Changed files
git log origin/main..HEAD --oneline # Commit history
| Branch prefix | Commit prefix | |---------------|---------------| | feature/ | feat | | fix/ | fix | | refactor/ | refactor | | perf/ | perf | | test/ | test | | docs/ | docs | | build/ | build | | ci/ | ci | | chore/ | chore |
If push succeeded but PR creation failed:
gh pr create --title "Title" --body "Message" --base main
development
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
development
Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.
development
Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
development
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.