
Pr Workflow
A solid set of guardrails for Claude when it's working in GitHub repos, especially as an automated action. Covers the basics you'd want enforced: atomic commits, clean PR hygiene, not mixing refactors with logic changes, and security essentials like keeping secrets out of version control. The CI-specific notes are the useful part here, explicitly allowing WIP commits and PRs when running in GitHub Actions with turn limits, which prevents the frustrating scenario where Claude tries to perfect everything in one shot. Also includes practical rules about looking up API docs instead of guessing and tracking third-party licenses properly. Nothing groundbreaking, but it'll save you from reviewing messy PRs or cleaning up credential leaks.
- skills.sh installs
- 1.2K
- GitHub stars
- 25.2K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add tursodatabase/turso --skill pr-workflow --agent claude-codeInstalls into .claude/skills of the current project.
Files
PR Workflow Guide
Commit Practices
- Atomic commits. Small, focused, single purpose
- Don't mix: logic + formatting, logic + refactoring
- Good message = easy to write short description of intent
Learn git rebase -i for clean history.
PR Guidelines
- Keep PRs focused and small
- Run relevant tests before submitting
- Each commit tells part of the story
CI Environment Notes
If running as GitHub Action:
- Max-turns limit in
.github/workflows/claude.yml - OK to commit WIP state and push
- OK to open WIP PR and continue in another action
- Don't spiral into rabbit holes. Stay focused on key task
Security
Never commit:
.envfiles- Credentials
- Secrets
Third-Party Dependencies
When adding:
- Add license file under
licenses/ - Update
NOTICE.mdwith dependency info
External APIs/Tools
- Never guess API params or CLI args
- Search official docs first
- Ask for clarification if ambiguous
Sponsors
Details
- Repository
- github.com/tursodatabase/turso
- Categories
- Security, Git & Pull Requests, Automation & Workflows, Databases
- First seen
- May 16, 2026