pivotdude-git-ai 1.0.1

package/dist/prompts/branch-commit-pr.md

@@ -0,0 +1,28 @@
+Analyze the staged diff and produce:
+1) branch name following repo conventions
+2) commit message in Conventional Commits format
+3) PR description for reviewers
+
+Response format (strict):
+BRANCH: <type>/<slug>
+COMMIT: <type>[scope]: description
+<optional body with bullet points>
+PR_DESC:
+<markdown, structured for readability>
+
+Rules:
+- Branch: lowercase, hyphens, short
+- Commit title: imperative mood, no trailing period, capitalize first word
+- Commit body: bullet points with notable changes only
+
+PR_DESC guidelines:
+- Start with a 1-2 sentence summary of what this PR does
+- For small changes (< 5 files): concise description is fine
+- For medium/large changes (5+ files, migrations, new features): include relevant sections from:
+  - **Motivation** — what problem this solves and why it matters (connect to real scenarios, not just code mechanics)
+  - **Key changes** — what changed and why this approach was chosen
+  - **Impact** — affected modules, database, performance, or compatibility notes
+  - **Testing notes** — how to verify correctness, edge cases, manual checks needed
+  - **Breaking?** — only if the change requires migration or has backward-incompatible effects
+- If the diff touches frontend files (apps/web/, .svelte, .css, .astro): include a **Screenshots** section — even if you don't have an actual screenshot, the placeholder tells the author what to add before merging
+- Focus on reviewer comprehension: the goal is to make the reviewer understand context and decisions without reading every diff line

package/dist/prompts/branch-commit-push.md

@@ -0,0 +1,13 @@
+Analyze the staged diff and produce:
+1) branch name following repo conventions
+2) commit message in Conventional Commits format
+
+Response format (strict):
+BRANCH: <type>/<slug>
+COMMIT: <type>[scope]: description
+<optional body with bullet points>
+
+Rules:
+- Branch: lowercase, hyphens, short
+- Commit title: imperative mood, no trailing period, capitalize first word
+- Commit body: bullet points with notable changes only

package/dist/prompts/commit-push.md

@@ -0,0 +1,10 @@
+Analyze the staged diff and produce a commit message.
+
+Response format (strict):
+COMMIT: <type>[scope]: description
+<optional body with bullet points>
+
+Rules:
+- Conventional Commits format
+- Commit title: imperative mood, no trailing period, capitalize first word
+- Body: bullet points with notable changes only

package/dist/prompts/create-pr.md

@@ -0,0 +1,25 @@
+Analyze all commits and file changes on the current branch compared to the base branch. Produce a PR title and description for reviewers.
+
+The input includes the commit log and full diff for everything that would land in this PR.
+
+Response format (strict):
+PR_TITLE: <type>[scope]: description
+PR_DESC:
+<markdown, structured for readability>
+
+Rules:
+- Title: imperative mood, no trailing period, capitalize first word
+- Title should reflect the full branch scope, not just the latest commit
+- Use Conventional Commits style for the title when it fits the changes
+
+PR_DESC guidelines:
+- Start with a 1-2 sentence summary of what this PR does
+- For small changes (< 5 files): concise description is fine
+- For medium/large changes (5+ files, migrations, new features): include relevant sections from:
+  - **Motivation** — what problem this solves and why it matters (connect to real scenarios, not just code mechanics)
+  - **Key changes** — what changed and why this approach was chosen
+  - **Impact** — affected modules, database, performance, or compatibility notes
+  - **Testing notes** — how to verify correctness, edge cases, manual checks needed
+  - **Breaking?** — only if the change requires migration or has backward-incompatible effects
+- If the diff touches frontend files (apps/web/, .svelte, .css, .astro): include a **Screenshots** section — even if you don't have an actual screenshot, the placeholder tells the author what to add before merging
+- Focus on reviewer comprehension: the goal is to make the reviewer understand context and decisions without reading every diff line

package/dist/prompts/git-conventions.md

@@ -0,0 +1,102 @@
+# Git Conventions
+
+This file defines the preferred branch naming and commit message format for this repository.
+
+Use it for human work and agent-generated git output.
+
+## Branch Naming
+
+Use lowercase, short, descriptive names.
+
+Preferred format:
+
+```text
+<type>/<short-kebab-slug>
+```
+
+Examples:
+
+- `feature/chart-toolbar`
+- `bugfix/ws-reconnect`
+- `refactor/backend-health-module`
+- `docs/update-readme`
+- `test/profile-page`
+- `chore/deps-refresh`
+
+## Allowed Branch Types
+
+- `feature` - new functionality
+- `bugfix` - bug fixes
+- `hotfix` - urgent production fix
+- `docs` - documentation changes
+- `refactor` - structural code changes without intended behavior change
+- `test` - tests or test infrastructure
+- `chore` - maintenance, tooling, or cleanup
+
+## Branch Rules
+
+- use lowercase only;
+- use hyphens inside the slug;
+- keep names short and readable;
+- avoid spaces, camelCase, snake_case, dots, and repeated hyphens.
+
+## Commit Format
+
+Use Conventional Commit style:
+
+```text
+<type>[<scope>]: <description>
+```
+
+Examples:
+
+- `feat(chart): add timeframe switcher`
+- `fix(auth): handle expired session redirect`
+- `docs(readme): update workspace guidance`
+- `refactor(websocket): simplify subscription cleanup`
+
+## Allowed Commit Types
+
+- `feat`
+- `fix`
+- `docs`
+- `refactor`
+- `test`
+- `chore`
+- `perf`
+- `style`
+- `build`
+- `ci`
+
+## Commit Rules
+
+- use imperative mood;
+- capitalize the first word of the description;
+- do not end the title with a period;
+- keep the title concise;
+- keep the scope short and meaningful when used.
+
+## Commit Body
+
+If a body is needed, use flat markdown bullets:
+
+```text
+<type>[<scope>]: <description>
+
+- Change 1
+- Change 2
+- Change 3
+```
+
+Use the body for:
+
+- notable implementation details;
+- affected areas;
+- important migration or compatibility notes.
+
+## What To Avoid
+
+- vague branch names like `fixes` or `update-stuff`
+- commit titles without a type prefix
+- long narrative paragraphs in commit bodies
+- mixing unrelated changes in one commit

package/package.json

@@ -0,0 +1,67 @@
+{
+  "name": "pivotdude-git-ai",
+  "version": "1.0.1",
+  "description": "AI-assisted git workflows: commit messages, branches, and pull requests",
+  "keywords": [
+    "git",
+    "ai",
+    "cli",
+    "commit",
+    "pull-request",
+    "conventional-commits"
+  ],
+  "type": "module",
+  "bin": {
+    "git-ai": "./bin/git-ai.js"
+  },
+  "files": [
+    "bin",
+    "dist",
+    "README.md",
+    "LICENSE",
+    "CHANGELOG.md",
+    "config.schema.json",
+    "project-config.example"
+  ],
+  "publishConfig": {
+    "access": "public",
+    "tag": "latest"
+  },
+  "repository": "github:pivotdude/git-ai",
+  "bugs": {
+    "url": "https://github.com/pivotdude/git-ai/issues"
+  },
+  "license": "MIT",
+  "scripts": {
+    "start": "bun run src/index.ts",
+    "check": "bunx tsc --noEmit",
+    "test": "bun test",
+    "lint:check": "eslint . --cache --cache-strategy content --cache-location .eslintcache",
+    "lint:fix": "eslint . --cache --cache-strategy content --cache-location .eslintcache --fix",
+    "fix": "bun run lint:fix",
+    "build": "bun build src/index.ts --outdir dist --target bun && bun run build:assets",
+    "build:assets": "mkdir -p dist/prompts && cp -r src/prompts/. dist/prompts/ && cp src/clients/cursor-sdk-runner.mjs dist/cursor-sdk-runner.mjs",
+    "prepublishOnly": "bun run build",
+    "verify": "bun run check && bun run test && bun run build",
+    "validate:local-release": "bash scripts/validate-local-release.sh",
+    "audit:private-artifacts": "bash scripts/audit-private-artifacts.sh"
+  },
+  "dependencies": {
+    "@connectrpc/connect-node": "^1.6.1",
+    "@cursor/sdk": "^1.0.19",
+    "ignore": "^7.0.5"
+  },
+  "devDependencies": {
+    "@eslint/js": "^10.0.1",
+    "@types/bun": "^1.3.14",
+    "eslint": "^10.6.0",
+    "eslint-config-prettier": "^10.1.8",
+    "globals": "^17.7.0",
+    "typescript": "5.9.3",
+    "typescript-eslint": "^8.62.1"
+  },
+  "engines": {
+    "bun": ">=1.3.0",
+    "node": ">=22"
+  }
+}

package/project-config.example/config.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "../config.schema.json",
+  "baseBranch": "main",
+  "prTemplate": ".github/PULL_REQUEST_TEMPLATE.md",
+  "stagedFix": {
+    "rules": [
+      {
+        "paths": ["src/**"],
+        "command": "npm run lint:fix"
+      }
+    ],
+    "root": null
+  }
+}

package/project-config.example/diff-ignore

@@ -0,0 +1,10 @@
+# .gitignore-style patterns omitted from AI diff prompts.
+# Merged with built-in lockfile defaults.
+
+bun.lock
+package-lock.json
+yarn.lock
+pnpm-lock.yaml
+
+# Generated assets
+# dist/**

package/project-config.example/prompts/commit-push.md

@@ -0,0 +1,14 @@
+Analyze the staged diff and produce a commit message.
+
+Follow the git conventions section below.
+
+Output format (plain text, no markdown fences):
+
+```
+<type>[<scope>]: <Title>
+
+- Bullet 1
+- Bullet 2
+```
+
+Return only the commit message block.