git-branching

Name: git-branching
Author: sriverogalan

Better Screenshoot branch, PR, and release rules

by sriverogalan(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from sriverogalan/better-screenshoot (.cursor/rules/git-branching.mdc). Copyright stays with the author.

Git: branches and releases

Branches

main is production. Releases are cut from main only.
develop is integration. Feature PRs target develop by default.
New branches from develop: feat/*, fix/*, chore/*, release/*.
PRs to main; title [better-screenshoot] ….

Commits

Conventional Commits: feat:, fix:, chore:, docs:, ci:.
One PR = one goal. Don't mix feature + version bump without reason.

Versions

Bump only the root package.json version. CI syncs the rest on PRs (pnpm sync-version). Targets: Cargo.toml, tauri.conf.json, and workspace package.json files.

Releases

Semver tag from main: v0.2.0.
Build and upload locally from main: pnpm release:mac v0.2.0 --all-arch (script exits on other branches).
See docs/branching.md for the full flow.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/sriverogalan-better-screenshoot-git-branching-rule/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

sriverogalan-better-screenshoot-git-branching-rule.ocm.jsonjson

{
  "ocm": "1",
  "id": "sriverogalan-better-screenshoot-git-branching-rule",
  "kind": "skill",
  "name": "git-branching",
  "description": "Better Screenshoot branch, PR, and release rules",
  "publisher": "sriverogalan",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "github-cursor-rules"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Better Screenshoot branch, PR, and release rules"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-cursor-rules",
      "repository": "https://github.com/sriverogalan/better-screenshoot",
      "path": ".cursor/rules/git-branching.mdc",
      "ref": "f74337f3885826da387964d61feba115cc58cf66",
      "url": "https://github.com/sriverogalan/better-screenshoot/blob/f74337f3885826da387964d61feba115cc58cf66/.cursor/rules/git-branching.mdc",
      "key": "sriverogalan/better-screenshoot/.cursor/rules/git-branching.mdc"
    }
  },
  "instructions": "# Git: branches and releases\n\n## Branches\n\n- `main` is production. Releases are cut from `main` only.\n- `develop` is integration. Feature PRs target `develop` by default.\n- New branches from `develop`: `feat/*`, `fix/*`, `chore/*`, `release/*`.\n- PRs to `main`; title `[better-screenshoot] …`.\n\n## Commits\n\n- Conventional Commits: `feat:`, `fix:`, `chore:`, `docs:`, `ci:`.\n- One PR = one goal. Don't mix feature + version bump without reason.\n\n## Versions\n\nBump only the root `package.json` version. CI syncs the rest on PRs (`pnpm sync-version`). Targets: `Cargo.toml`, `tauri.conf.json`, and works",
  "cost": {
    "context_tokens": 208
  }
}

Fetch it by URL: GET /api/v1/registry/sriverogalan-better-screenshoot-git-branching-rule/manifest?version=1.0.0