awesome-coolify / rules
Cursor rule0 starsChanged 4 months agoMITView on GitHub
After /gsd-ship creates a PR, always run gsd-ship-post (labels + optional changeset)
- 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,181 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 repository4 other files it gives its agents.
- coolify-deploySkill
- coolify-diagnoseSkill
- coolify-incidentSkill
- coolify-setupSkill
The file
We split this gsd-ship-labels.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 7
When /gsd-ship (or any flow that runs gh pr create for a GSD phase) succeeds:
- Very specific: line 39
If the Cursor afterShellExecution hook already ran gsd-ship-post, verify labels are present and skip a duplicate run.
≈ “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
--- description: After /gsd-ship creates a PR, always run gsd-ship-post (labels + optional changeset) alwaysApply: true --- # GSD Ship → Labels + Optional Changeset (mandatory) When `/gsd-ship` (or any flow that runs `gh pr create` for a GSD phase) succeeds: 1. **Immediately** run: ```bash ./scripts/gsd-ship-post.sh <pr-number> ``` This is non-optional. By default it: - Applies ship labels via `scripts/gsd-pr-labels.sh --mode ship` **including `automerge`** - Clears `needs-changeset` so Kodiak can merge phase PRs without a changeset - Strips Kodiak blockers (`status: needs-review`, etc.) - Does **not** create a `.changeset/` file (milestone-only npm release model) For hotfix / out-of-band releases that need an immediate changeset: ```bash ./scripts/gsd-ship-post.sh <pr-number> --with-changeset ``` That opt-in path runs `gsd-ensure-changeset.sh`, commits + pushes the fragment, then applies ship labels. Kodiak still only merges when required CI checks are green — `automerge` is the opt-in, not a force-merge. **Never push `[ci skip]` / `[skip ci]` onto a PR tip.** Required checks (`Lint, Test & Build`, `MegaLinter`) are bound to HEAD; a skipped tip leaves them stuck at "Expected — Waiting for status to be reported" and Kodiak waits forever. 2. Preview: ```bash ./scripts/gsd-ship-post.sh <n> --dry-run ``` If the Cursor `afterShellExecution` hook already ran `gsd-ship-post`, verify labels are present and skip a duplicate run.
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.