AI SummaryWedjat provides comprehensive Gitflow workflow rules for Cursor, defining branch strategies, naming conventions, and merge policies to standardize git operations. Developers using Cursor will benefit from having clear, enforced guidelines for feature development, releases, and hotfixes.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "wedjat — Cursor Rules" prompt rules to my project. Repository: https://github.com/daskinnyman/wedjat 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
Gitflow Workflow Rules. These rules should be applied when performing git operations.
main (or master)
• Contains production-ready code • Never commit directly to main • Only accepts merges from: • hotfix/\* branches • release/\* branches • Must be tagged with version number after each merge
develop
• Main development branch • Contains latest delivered development changes • Source branch for feature branches • Never commit directly to develop
feature/\*
• Branch from: develop • Merge back into: develop • Naming convention: feature/[issue-id]-descriptive-name • Example: feature/123-user-authentication • Must be up-to-date with develop before creating PR • Delete after merge
release/\*
• Branch from: develop • Merge back into: • main • develop • Naming convention: release/vX.Y.Z • Example: release/v1.2.0 • Only bug fixes, documentation, and release-oriented tasks • No new features • Delete after merge
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