react-ts-vite / rules
Cursor rule1 starsChanged 25 days agoMITView on GitHub
Commit conventions, pull-request hygiene and how releases and deployment reports are produced.
- Reads credentials
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,183 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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/rtv-architecture.mdcCursor rule
- .cursor/rules/rtv-code-style.mdcCursor rule
- .cursor/rules/rtv-design-system.mdcCursor rule
- .cursor/rules/rtv-testing.mdcCursor rule
- accessibility-auditSkill
- ci-cd-dockerSkill
- clean-code-reviewSkill
- dependency-upgradeSkill
- deployment-insightsSkill
- project-architectureSkill
- react-componentSkill
- scaffold-featureSkill
- tailwind-design-systemSkill
- testing-vitestSkill
The file
We split this rtv-git-workflow.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Changelog: add a line under ## [Unreleased] in CHANGELOG.md for every user-visible change (Keep a Changelog format).
≈ “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: "Commit conventions, pull-request hygiene and how releases and deployment reports are produced." globs: alwaysApply: true --- <!-- rtv:generated --> <!-- Generated from .agent/rules/git-workflow.md by `npm run agent:sync`. --> # Git workflow - **Conventional Commits**: `feat:`, `fix:`, `docs:`, `refactor:`, `test:`, `chore:`, `ci:`, `build:`, `perf:`, with an optional scope (`feat(dashboard): add period filter`). Subject in the imperative, ≤ 72 characters, body explains _why_. - **Branches**: `feat/<topic>`, `fix/<topic>`, `chore/<topic>` from `master`. One concern per branch; keep PRs reviewable (< ~400 changed lines when possible). - **Before pushing**: `npm run check` must pass locally; CI runs the same gate on Node 22 and 24 plus an architecture-switch smoke test. - **Pull requests** describe the change, how it was tested and any follow-ups. Link issues. Generated files (`AGENTS.md`, mirrors, lockfile) are committed together with the change that produced them. - **Changelog**: add a line under `## [Unreleased]` in `CHANGELOG.md` for every user-visible change (Keep a Changelog format). - **Release**: bump `version` in `package.json` (`npm version <patch|minor|major> --no-git-tag-version`), move Unreleased into a dated changelog section, commit `chore(release): vX.Y.Z` and merge it into the `release` branch. The `Release` workflow (`.github/workflows/release.yml`) runs the quality gate, tags `vX.Y.Z`, publishes the GitHub release from the changelog section, publishes to npm with provenance and, when `ANTHROPIC_API_KEY` is configured, appends a Claude deployment report. Never tag by hand. - **Never** rewrite shared history (`push --force` on `master`), commit `.env` files or credentials, or merge with a red CI.
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.