npx agentspec-cli install cd665eff-5460-4699-8256-f4ac67a220f4 --file-type cursor-rules→ .cursor/rules/
--- description: Git workflow and commit rules globs: ["**/*"] --- # Git Rules ## Branch Strategy - `main` - Production-ready, protected - `feat/*` - New features - `fix/*` - Bug fixes - `docs/*` - Documentation - `refactor/*` - Code restructuring ## Before Starting Work ALWAYS sync with main: ```bash git checkout main git fetch origin git pull origin main git checkout -b feat/your-feature ``` ## Commit Messages Follow [Conventional Commits](https://conventionalcommits.org): ``` <type>(<scope>): <description> [optional body] [optional footer] ``` ### Types | Type | Description | Version Bump | |------|-------------|--------------| | `feat` | New feature | Minor (0.x.0) | | `fix` | Bug fix | Patch (0.0.x) | | `docs` | Documentation | None | | `style` | Formatting | None | | `refactor` | Restructuring | None | | `perf` | Performance | Patch | | `test` | Tests | None | | `chore` | Maintenance | None | ### Examples ```bash feat: add restore command for backup recovery fix: handle missing config file gracefully docs: update installation instructions refactor: extract git operations to lib/git.ts test: add integration tests for sync command chore: update dependencies ``` ### Breaking Changes ```bash feat!: redesign configuration format BREAKING CHANGE: Config files must be migrated ``` ## Before Committing Run all checks: ```bash pnpm lint && pnpm typecheck && pnpm test ``` ## Pull Requests 1. Create against `main` 2. Wait for CI to pass 3. Request review 4. Address feedback 5. Merge when approved ## NEVER Do - Force push to main - Skip CI checks - Merge without review - Commit directly to main
Git Workflow
Cursor IDE rules and conventions for AI-assisted development.
by AgentHub Crawler
Git Workflow Standards
When working on any new plan or feature, follow this git workflow consistently.
by AgentHub Crawler
Project Instructions
**Never push directly to `main`.** All changes must go through a pull request: 0. Always create a branch specific to the change before committing: `feat/`, `fix/`, `docs/`, `chore/`, `test/`, etc. 1. Push the branch and open a PR — never `git push origin main`.
by AgentHub Crawler
Sign in to leave a comment.
Gitflow Workflow Rules
1. All changes must go through Pull Requests 2. Required approvals: minimum 1 3. CI checks must pass 4. No direct commits to protected branches (main, develop) 5. Branch must be up to date before merging
by AgentHub Crawler