create-pull-request
Skill0 starsChanged 7 months agoMITView on GitHub
Use this skill when creating or updating a pull request in the TTA.dev repository. Covers PR structure, review expectations, and checklist.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- ErikaAX08/erikas-skillstheir own version, first seen Nov 8, 2026
- marcellocurto/skillstheir own version, first seen Nov 8, 2026
- openflocon/Flocontheir own version, first seen Nov 1, 2026
- StephanMeijer/skillstheir own version, first seen Nov 1, 2026
- tada5hi/skillstheir own version, first seen Nov 1, 2026
- vrodokanakis/claude-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use grilling and frontend-design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkillgrilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- cline/cline★ 71ksame name
- makeplane/plane★ 62ksame name
- bitwarden/clients★ 14ksame name
- microsoft/vscode-pull-request-github★ 2.6ksame name
- Mapsui/Mapsui★ 1.6ksame name
- warpdotdev/oz-skills★ 825same name
- platformplatform/PlatformPlatform★ 439same name
- openflocon/Flocon★ 379same name
- haru/redmine_ai_helper★ 107same name
- braintrustdata/braintrust-sdk★ 30same name
17 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/tta-dev.mdcCursor rule
- build-test-verifySkill
- core-conventionsSkill
- create-atomic-noteSkill
- git-commitSkill
- sdd-workflowSkill
- self-review-checklistSkill
- session-startSkill
- build-test-verifySkill
- core-conventionsSkill
- create-agentSkill
- create-atomic-noteSkill
- create-pull-requestSkill
- Feature DevelopmentSkill
- git-commitSkill
- Incident ResponseSkill
- Package ReleaseSkill
- sdd-workflowSkill
- self-review-checklistSkill
- session-startSkill
- ttadev-llmSkill
- ttadev-primitivesSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 12
Follow Conventional Commits format: <type>: <description>
- Very specific: line 41
Run the full quality gate (see build-test-verify skill).
- Distinctive: line 43
Ensure all new code uses primitives for workflow patterns.
- Distinctive: line 44
Verify no secrets or credentials are committed.
“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 introducedBefore 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.