AI SummaryA Windsurf rules collection that guides AI coding assistants to implement Gitflow branching workflows and best practices. Useful for teams adopting structured version control and release management processes.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "vibe-rules-collection — Windsurf Rules" prompt rules to my project. Repository: https://github.com/copyleftdev/vibe-rules-collection Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
A curated collection of .windsurfrules files designed to guide AI coding assistants (like Codeium's Cascade) in generating code that adheres to various best practices, architectural patterns, language idioms, and framework conventions.
Guiding Principles
• Main Branches: • main (or master): Represents production-ready code. Only receives merges from release branches or hotfixes. Should always be stable. • develop: Integration branch for features. Represents the latest delivered development changes for the next release. Origin for feature branches, target for merges from feature branches. • Supporting Branches: • feature/*: Branched from develop. Used for developing new features. Merged back into develop when complete. • release/: Branched from develop when ready to prepare a new production release. Allows for final testing, bug fixes, and documentation specific to the release. Merged into main and* develop upon release. • hotfix/: Branched from main. Used to fix critical bugs in production directly. Merged back into main and* develop after fixing. • Tagging: Tag commits on main with version numbers (e.g., v1.0.0) upon release. • Workflow: • Start new features off develop (feature/my-feature). • Merge completed features into develop. • When develop has enough features for a release, branch release/vX.Y.Z from develop. • Perform release prep (testing, bugfixes) on the release branch. Merge necessary fixes back into develop periodically. • When release is ready, merge release/vX.Y.Z into main and tag main. • Merge release/vX.Y.Z back into develop to incorporate release fixes. • For urgent production bugs, branch hotfix/issue-XYZ from main, fix, merge to main, tag, merge back to develop. • Suited For: Projects with scheduled release cycles, where maintaining multiple versions in production might be necessary.
AI Instructions
• Branch Creation: Generate commands to create branches following Gitflow naming conventions and branching from the correct base (git checkout -b feature/x develop, git checkout -b release/y develop, git checkout -b hotfix/z main). • Merge Targets: Generate merge commands targeting the correct branches (git checkout develop && git merge feature/x, git checkout main && git merge release/y, git checkout develop && git merge release/y, etc.). • Tagging Commands: Generate commands for creating annotated tags (git tag -a vX.Y.Z -m "Version X.Y.Z"). • Workflow Guidance: Explain the next step in the Gitflow process based on the current context (e.g., "After finishing the feature, merge it into develop", "To start a release, branch from develop").
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts