PR Workflow Guide
SkillDatabases & dataGeneral guidelines for Commits, formatting, CI, dependencies, security
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the PR Workflow Guide skill
What this skill tells your AI
The instructions your AI receives, as published by tursodatabase/turso-vdbe-doom-example in .claude/skills/pr-workflow/SKILL.md and read by ahel’s review.
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
Signals
- GitHub stars
- 36
- Forks
- 2
- Last commit
- Jul 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
pr-workflow-2- Source
- github.com/tursodatabase/turso-vdbe-doom-example