Create pull request
Skill theinterneti/TTA.dev/.github/skills/create-pull-request
AI devops for vibe coders
npx -y skills add theinterneti/TTA.dev --skill create-pull-requestAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use this skill when creating or updating a pull request in the TTA.dev repository. Covers PR title format, description template, review expectations, and pre-submit checklist. Invoke when the user says "create a PR", "open a pull request", "submit my changes", or "make a PR".
SKILL.md
1.4 KB, 262 tokens by cl100k_base, as published. Nobody here has run it
Create Pull Request (TTA.dev)
Guide for creating well-structured pull requests.
PR Title
Follow Conventional Commits format: <type>: <description>
Examples:
feat: add CachePrimitive metrics integrationfix: resolve timeout in RetryPrimitive backoffdocs: update primitives catalog with new skills API
PR Description Template
## Summary
Brief description of what this PR does.
## Changes
- List of specific changes made.
## Testing
- How the changes were tested.
- Coverage impact.
## Checklist
- [ ] Quality gate passes (format, lint, type check, tests)
- [ ] 100% test coverage on new code
- [ ] Documentation updated if applicable
- [ ] No new anti-patterns introduced
Before Submitting
- Run the full quality gate (see
build-test-verifyskill). - Self-review your diff (see
self-review-checklistskill). - Ensure all new code uses primitives for workflow patterns.
- Verify no secrets or credentials are committed.
Deep Reference
For full Python coding standards, see docs/agent-guides/python-standards.md.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most pr commit review skills give in 262 tokens
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07
- Use conventional commits formatin 127 of 888, across 115 files
- Keep subject line under 72 charactersin 62 of 888, across 48 files
- Delete branches after mergein 51 of 888, across 38 files
- Use imperative mood in subject linein 51 of 888, across 42 files
- Use imperative mood in commit messagesin 44 of 888
- Verify directory is ignored before creating worktreein 43 of 888, across 12 files
- Generate a conventional commit messagein 43 of 888
- Add unignored worktree directories to gitignorein 42 of 888, across 10 files
- Make atomic commitsin 39 of 888, across 27 files
- Run tests before committingin 36 of 888, across 25 files
- Verify clean test baselinein 35 of 888, across 9 files
- Split unrelated changes into separate commitsin 35 of 888, across 30 files
Said here and by no other author read
- list specific changes made in the PR
- run the full quality gate before submitting
- use primitives for all new workflow code
- verify no secrets are committed
- ensure quality gate passes
- maintain 100% test coverage on new code
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.