Gitflow Agent Rule
Gitflow Workflow Rules. These rules should be applied when performing git operations.
Structured JSON Schema
Use with automated API pipelines, LangChain, or custom image generators
{
"system_prompt": "# Gitflow Workflow Rules\n\n## Main Branches\n\n### main (or master)\n- Contains production-ready code\n- Never commit directly to main\n- Only accepts merges from:\n - hotfix/* branches\n - release/* branches\n- Must be tagged with version number after each merge\n\n### develop\n- Main development branch\n- Contains latest delivered development changes\n- Source branch for feature branches\n- Never commit directly to develop\n\n## Supporting Branches\n\n### feature/*\n- Branch from: develop\n- Merge back into: develop\n- Naming convention: feature/[issue-id]-descriptive-name\n- Example: feature/123-user-authentication\n- Must be up-to-date with develop before creating PR\n- Delete after merge\n\n### release/*\n- Branch from: develop\n- Merge back into: \n - main\n - develop\n- Naming convention: release/vX.Y.Z\n- Example: release/v1.2.0\n- Only bug fixes, documentation, and release-oriented tasks\n- No new features\n- Delete after merge\n\n### hotfix/*\n- Branch from: main\n- Merge back into:\n - main\n - develop\n- Naming convention: hotfix/vX.Y.Z\n- Example: hotfix/v1.2.1\n- Only for urgent production fixes\n- Delete after merge\n\n## Commit Messages\n\n- Format: `type(scope): description`\n- Types:\n - feat: New feature\n - fix: Bug fix\n - docs: Documentation changes\n - style: Formatting, missing semicolons, etc.\n - refactor: Code refactoring\n - test: Adding tests\n - chore: Maintenance tasks\n\n## Version Control\n\n### Semantic Versioning\n- MAJOR version for incompatible API changes\n- MINOR version for backwards-compatible functionality\n- PATCH version for backwards-compatible bug fixes\n\n## Pull Request Rules\n\n1. All changes must go through Pull Requests\n2. Required approvals: minimum 1\n3. CI checks must pass\n4. No direct commits to protected branches (main, develop)\n5. Branch must be up to date before merging\n6. Delete branch after merge\n\n## Branch Protection Rules\n\n### main & develop\n- Require pull request reviews\n- Require status checks to pass\n- Require branches to be up to date\n- Include administrators in restrictions\n- No force pushes\n- No deletions\n\n## Release Process\n\n1. Create release branch from develop\n2. Bump version numbers\n3. Fix any release-specific issues\n4. Create PR to main\n5. After merge to main:\n - Tag release\n - Merge back to develop\n - Delete release branch\n\n## Hotfix Process\n\n1. Create hotfix branch from main\n2. Fix the issue\n3. Bump patch version\n4. Create PR to main\n5. After merge to main:\n - Tag release\n - Merge back to develop\n - Delete hotfix branch",
"prompt_type": "agent_rule",
"framework": "cursor",
"globs": "[\"**/*\"]",
"compatible_models": [
"Claude 3.5 Sonnet",
"GPT-4o",
"Cursor AI",
"Gemini 2.5 Flash"
],
"download_filename": "gitflow.cursorrules",
"tags": [
"cursor",
"cursorrules",
"agent",
"coding",
"gitflow"
]
}
Voice Search & FAQs
Natural voice queries and direct answers for Siri, Google Assistant & Perplexity
"What is the best AI Agents prompt for Cursor AI / Claude 3.5?"
The Gitflow Agent Rule blueprint is optimized for Cursor AI / Claude 3.5 to produce high-precision output with verified JSON formatting.
"How do I prompt Cursor AI / Claude 3.5 for Gitflow Agent Rule?"
Use the verified Gitflow Agent Rule prompt from JsonPrompts.in. Copy the prompt or structured JSON blueprint and paste it directly into Cursor AI / Claude 3.5.
"Where can I find free Cursor AI / Claude 3.5 prompt templates for AI Agents?"
JsonPrompts.in offers free verified AI Agents JSON prompt blueprints including Gitflow Agent Rule, with zero sign-up required.