agentleFS
Sign inStart free
RojiosRojios/everything-claude-code/.cursor/rules/common-development-workflow.md

everything-claude-code / rules

Cursor rule1 starsChanged 7 months agoMITView on GitHub

Development workflow: plan, TDD, review, commit pipeline

19 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this common-development-workflow.md into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use planner agent to create implementation plan

    line 14
  2. Distinctive:

    Write tests first (RED)

    line 20
  3. Distinctive:

    Use code-reviewer agent immediately after writing code

    line 26
  4. Distinctive:

    Follow conventional commits format

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
common-development-workflow.md

Development Workflow

This rule extends the git workflow rule with the full feature development process that happens before git operations.

The Feature Implementation Workflow describes the development pipeline: planning, TDD, code review, and then committing to git.

Feature Implementation Workflow

  1. Plan First
    • Use planner agent to create implementation plan
    • Identify dependencies and risks
    • Break down into phases
  2. TDD Approach
    • Use tdd-guide agent
    • Write tests first (RED)
    • Implement to pass tests (GREEN)
    • Refactor (IMPROVE)
    • Verify 80%+ coverage
  3. Code Review
    • Use code-reviewer agent immediately after writing code
    • Address CRITICAL and HIGH issues
    • Fix MEDIUM issues when possible
  4. Commit & Push
    • Detailed commit messages
    • Follow conventional commits format
    • See the git workflow rule for commit message format and PR process

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free