pr-workflow — Claude Code skill: what it does, how to install
Enforces rules for atomic commits, clean PRs, dependency licensing, and secret hygiene. Useful for agents pushing code or running inside CI workflows.
npx skills add tursodatabase/turso --skill pr-workflow -a claude-codeWhat pr-workflow does
This skill defines standards for code contributions. It instructs the agent to create atomic commits, separating logic changes from formatting or refactoring. Commits must never include .env files, credentials, or secrets. Before opening a PR, the agent runs relevant tests and keeps changes small.
When adding third-party dependencies, the agent must save the license file into licenses/ and update NOTICE.md. It forbids guessing API parameters or CLI arguments, requiring the model to inspect official documentation first. If your repository lacks a licenses/ directory or NOTICE.md, these strict requirements will require manual adjustments.
For CI runs configured via .github/workflows/claude.yml, the skill accounts for GitHub Actions turn limits. Agents are permitted to commit WIP states and open draft PRs so they stay focused without getting stuck in loops.
What it helps with
- keep commit histories atomic without mixing logic and formatting
- prevent committing credentials, secrets, and
.envfiles - track third-party licenses in
licenses/andNOTICE.md - avoid GitHub Actions max-turn timeouts by pushing WIP commits
Example prompts for the agent
- Prepare a pull request with atomic commits and run the test suite before submitting.
- Add this dependency, place its license in licenses/ and update NOTICE.md.
- Check git status to ensure no .env files or secrets are staged.
How to install pr-workflow
1Skills CLI (Vercel)
npx skills add tursodatabase/turso --skill pr-workflow -a claude-code2Manually: put the files in place
~/.claude/skills/pr-workflow/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pr-workflow/
1Skills CLI (Vercel)
npx skills add tursodatabase/turso --skill pr-workflow -a codex2Manually: put the files in place
.agents/skills/pr-workflow/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tursodatabase/turso --skill pr-workflow -a cursor2Manually: put the files in place
.cursor/skills/pr-workflow/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tursodatabase/turso pr-workflow2Manually: put the files in place
.github/skills/pr-workflow/SKILL.md1Skills CLI (Vercel)
npx skills add tursodatabase/turso --skill pr-workflow -a gemini-cli2Platform CLI
gemini skills install https://github.com/tursodatabase/turso --path .claude/skills/pr-workflowManually: put the files in place
.devin/skills/pr-workflow/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tursodatabase/turso --skill pr-workflow -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set10
The whole set →Similar
Questions about pr-workflow
How do I install pr-workflow in Claude Code?
Run npx skills add tursodatabase/turso --skill pr-workflow -a claude-code. Alternatively, place the skill file directly at ~/.claude/skills/pr-workflow/SKILL.md.
What does the pr-workflow skill do?
It provides guidelines for clean git commits, pull request hygiene, and dependency tracking. It also prevents secret leaks and stops the agent from guessing CLI arguments.
How does pr-workflow handle GitHub Actions limits?
The skill acknowledges the max-turns limit in .github/workflows/claude.yml. It allows the agent to commit WIP code and open draft PRs to avoid hitting action execution limits.
Source text
SKILL.md · MIT
--- name: pr-workflow description: General guidelines for Commits, formatting, CI, dependencies, security --- # 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: - `.env` files - Credentials - Secrets ## Third-Party Dependencies When adding: 1. Add license file under `licenses/` 2. Update `NOTICE.md` with dependency info ## External APIs/Tools - Never guess API params or CLI args - Search official docs first - Ask for clarification if ambiguous
© tursodatabase · MIT · tursodatabase/turso