Skip to content

feat(rules): separate Feature Implementation Workflow from git-workflow.md (fixes #235)#278

Merged
affaan-m merged 2 commits into
affaan-m:mainfrom
pangerlkr:feat/separate-development-workflow-235
Feb 24, 2026
Merged

feat(rules): separate Feature Implementation Workflow from git-workflow.md (fixes #235)#278
affaan-m merged 2 commits into
affaan-m:mainfrom
pangerlkr:feat/separate-development-workflow-235

Conversation

@pangerlkr

@pangerlkr pangerlkr commented Feb 24, 2026

Copy link
Copy Markdown
Contributor

Description

Resolves #235

Splits the Feature Implementation Workflow out of rules/common/git-workflow.md into a new dedicated rules/common/development-workflow.md file.

Changes

  • rules/common/git-workflow.md: Removed the Feature Implementation Workflow section; now focuses exclusively on git-specific concerns (commit message format, PR workflow). Added a reference to the new development-workflow.md.
  • rules/common/development-workflow.md (new file): Contains the Feature Implementation Workflow (Plan First → TDD → Code Review → Commit & Push), with cross-reference back to git-workflow.md for commit format.

Type of Change

  • refactor: Code refactoring (moving content between files)
  • feat: New feature (new file development-workflow.md)

Summary by CodeRabbit

  • Documentation
    • Introduced comprehensive feature development workflow documentation detailing a structured four-step process: planning with task breakdown, test-driven development with coverage targets, code review procedures, and commit practices aligned with conventional standards.
    • Reorganized development guidance for improved clarity and streamlined reference across workflow documentation.

…low.md (refs affaan-m#235)

Removed the Feature Implementation Workflow section from the Git Workflow document.
…Workflow (refs affaan-m#235)

This document outlines the full feature development process, including planning, TDD, code review, and committing to git.
@coderabbitai

coderabbitai Bot commented Feb 24, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db27ba1 and 253aecb.

📒 Files selected for processing (2)
  • rules/common/development-workflow.md
  • rules/common/git-workflow.md

📝 Walkthrough

Walkthrough

The PR separates feature development workflow documentation from git-specific workflow concerns by extracting the four-step feature implementation process (Plan, TDD, Code Review, Commit) into a dedicated development-workflow.md file and consolidating git-workflow.md to focus exclusively on git-related operations with a reference to the new document.

Changes

Cohort / File(s) Summary
Documentation Refactoring
rules/common/git-workflow.md
Removed "Feature Implementation Workflow" section (23 lines) and replaced with a reference note directing readers to the new development-workflow.md for the complete development process.
New Development Documentation
rules/common/development-workflow.md
Created new file documenting the feature implementation workflow in four phases: Plan First (using planner agent), TDD Approach (RED-GREEN-REFACTOR-IMPROVE cycle with 80%+ coverage), Code Review (priority-based issue handling), and Commit & Push (conventional commit practices).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 whiskers wiggle with delight
Documentation scattered, now organized right—
Git keeps its workflow, clean and true,
Development gets its own stage too! ✨
A rabbit's joy: concerns separated through and through!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title clearly summarizes the main change: separating the Feature Implementation Workflow from git-workflow.md, which is the primary objective of this changeset.
Linked Issues check ✅ Passed The pull request fulfills all coding requirements from issue #235: it separates the Feature Implementation Workflow into a new development-workflow.md file and refocuses git-workflow.md on git-specific concerns.
Out of Scope Changes check ✅ Passed All changes are directly scoped to issue #235; the PR only modifies git-workflow.md and creates development-workflow.md with no extraneous modifications.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR resolves #235 by separating the general Feature Implementation Workflow from the git-focused guidance, keeping git-workflow.md narrowly scoped to git/PR concerns and moving development-process guidance into a new dedicated document.

Changes:

  • Removed the “Feature Implementation Workflow” section from rules/common/git-workflow.md and added a reference to the new doc.
  • Added rules/common/development-workflow.md containing the Feature Implementation Workflow and a cross-reference back to git-workflow.md.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
rules/common/git-workflow.md Removes non-git development-process guidance and links to the new development workflow doc.
rules/common/development-workflow.md New doc housing the end-to-end feature implementation workflow with a link back to git workflow details.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

4. **Commit & Push**
- Detailed commit messages
- Follow conventional commits format
> For the full development process (planning, TDD, code review) before git operations,

Copilot AI Feb 24, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrase "before git operations" is inaccurate now that the referenced development workflow includes a "Commit & Push" step (i.e., git operations). Consider rewording to something like "for the broader development process (planning, TDD, code review) that complements this git workflow" to avoid a contradiction.

Suggested change
> For the full development process (planning, TDD, code review) before git operations,
> For the broader development process (planning, TDD, code review) that complements this git workflow,

Copilot uses AI. Check for mistakes.
Comment on lines +3 to +5
> This file extends [common/git-workflow.md](./git-workflow.md) 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.

Copilot AI Feb 24, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This intro says the workflow "happens before git operations", but the file later includes "Commit & Push" which is a git operation. Reword the intro to avoid the internal inconsistency (e.g., describe it as the end-to-end development workflow including committing/pushing).

Suggested change
> This file extends [common/git-workflow.md](./git-workflow.md) 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.
> This file extends [common/git-workflow.md](./git-workflow.md) with the end-to-end feature development process, from planning through commit and push.
The Feature Implementation Workflow describes the end-to-end development pipeline: planning, TDD, code review, and then committing and pushing to git.

Copilot uses AI. Check for mistakes.
Comment on lines +3 to +5
> This file extends [common/git-workflow.md](./git-workflow.md) 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.

Copilot AI Feb 24, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The rules index in rules/README.md enumerates the files under rules/common/, but it doesn't include this new development-workflow.md. To keep the documentation consistent/discoverable, update the index to include the new file (and possibly clarify the separation between development vs git workflow).

Suggested change
> This file extends [common/git-workflow.md](./git-workflow.md) 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.
> This file complements [common/git-workflow.md](./git-workflow.md) by describing the feature implementation steps that happen **before** any git branching, committing, or PR activity.
The Feature Implementation Workflow covers the development pipeline (planning, TDD, code review) up to the point where changes are ready to be committed, while `git-workflow.md` documents how to manage branches, commits, and pull requests.

Copilot uses AI. Check for mistakes.

@affaan-m affaan-m left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review: doc-only changes look good. Approving.

@affaan-m affaan-m merged commit 5dad143 into affaan-m:main Feb 24, 2026
41 of 42 checks passed
FrancescoRosciano pushed a commit to FRosciano-Mambo/everything-claude-code that referenced this pull request Jun 1, 2026
…ent-workflow-235

feat(rules): separate Feature Implementation Workflow from git-workflow.md (fixes affaan-m#235)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Separate Feature Implementation Workflow from git-workflow.md

3 participants