aidd-template-scale / rules
Cursor rule0 starsChanged 2 months agoMITView on GitHub
GitHub CLI — PR and Issues
- Commits and pushes
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/CLAUDE.mdcCursor rule
- .cursor/rules/code-style.mdcCursor rule
- .cursor/rules/docker-compose-local.mdcCursor rule
- .cursor/rules/git.mdcCursor rule
- .cursor/rules/git-worktree.mdcCursor rule
- .cursor/rules/ticket-driven-workflow.mdcCursor rule
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
The file
We split this github-cli-pr.mdc into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use gh from the repository root (or --repo OWNER/REPO).
- Distinctive: line 43
If label creation fails (permissions), stop and ask the user.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
alwaysApply: true
description: GitHub CLI — PR and Issues
globs: **/*
---
# GitHub CLI — PR and Issues
Use **`gh`** from the repository root (or `--repo OWNER/REPO`).
## Version
Recommended: **gh v2.82.1+** (`gh --version`).
## Read PR / Issue
```bash
gh pr list
gh pr view <n>
gh pr diff <n>
gh pr checks <n>
gh issue view <n>
gh issue view <n> --comments
```
## Update title/body (REST PATCH)
`gh pr edit` / `gh issue edit` may fail on older GraphQL project APIs. Prefer REST:
```bash
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
gh api -X PATCH "/repos/${REPO}/pulls/<n>" -f title='...' -f body='...'
gh api -X PATCH "/repos/${REPO}/issues/<n>" -f title='...' -f body='...'
```
## Labels
```bash
gh label create in-progress --color FFAA00 --description "Work in progress" 2>/dev/null || true
gh issue edit <n> --add-label in-progress
```
If label creation fails (permissions), stop and ask the user.
## Create PR
```bash
gh pr create --base main --title "feat(#42): summary" --body "$(cat <<'EOF'
Fixes #42
## Summary
...
EOF
)"
```
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.