@fentech/gitcontext 0.3.3

package/src/templates/cursor/commands/capture-blocker.md

@@ -0,0 +1,27 @@
+# Capture Blocker
+
+Capture a blocker doc — something that is blocking or has blocked progress on a task or feature.
+
+## Steps
+
+1. Gather context from the current conversation and recent git history:
+   ```bash
+   git log --oneline -10
+   ```
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `blocker`
+   - `title`: concise description of what is blocked (e.g., "Cannot run migrations: DATABASE_URL_DIRECT not set in CI")
+   - `summary`: 2–4 sentences describing what is blocked, why, and current status
+   - `tags`: relevant keywords (e.g., `["ci", "migrations", "env"]`)
+   - `code_snippet` (optional): error output or relevant config
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+/capture-blocker
+/capture-blocker <optional: brief description to seed context>
+```

package/src/templates/cursor/commands/capture-bug.md

@@ -0,0 +1,28 @@
+# Capture Bug
+
+Capture a bug doc — a bug that was found, diagnosed, and fixed (or is being fixed).
+
+## Steps
+
+1. Gather context from the current conversation and recent git history:
+   ```bash
+   git log --oneline -10
+   git diff HEAD~1
+   ```
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `bug`
+   - `title`: concise description of the bug (e.g., "Auth token expiry check uses < instead of <=")
+   - `summary`: 2–4 sentences covering symptom, root cause, and fix
+   - `tags`: relevant keywords (e.g., `["auth", "token", "expiry"]`)
+   - `code_snippet` (optional): the fix or the problematic code
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+/capture-bug
+/capture-bug <optional: brief description to seed context>
+```

package/src/templates/cursor/commands/capture-convention.md

@@ -0,0 +1,24 @@
+# Capture Convention
+
+Capture a convention doc — a decision about how code should be structured, named, or written in this project.
+
+## Steps
+
+1. Gather context from the current conversation and relevant files in the repo.
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `convention`
+   - `title`: concise description of the convention (e.g., "Server functions must be defined in services/, not route files")
+   - `summary`: 2–4 sentences explaining the convention and why it exists
+   - `tags`: relevant keywords (e.g., `["architecture", "server-functions", "tanstack"]`)
+   - `code_snippet` (optional): example of the pattern in practice
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+/capture-convention
+/capture-convention <optional: brief description to seed context>
+```

package/src/templates/cursor/commands/capture-learning.md

@@ -0,0 +1,27 @@
+# Capture Learning
+
+Capture a learning doc — a new insight, technique, or understanding gained during development.
+
+## Steps
+
+1. Gather context from the current conversation and recent git history:
+   ```bash
+   git log --oneline -10
+   ```
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `learning`
+   - `title`: concise, specific (e.g., "Vite requires explicit file extensions for dynamic imports")
+   - `summary`: 2–4 sentences explaining the learning clearly
+   - `tags`: relevant keywords (e.g., `["vite", "esm", "bundler"]`)
+   - `code_snippet` (optional): illustrative code if applicable
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+/capture-learning
+/capture-learning <optional: brief description to seed context>
+```

package/src/templates/cursor/mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "gitcontext": {
+      "command": "gitcontext",
+      "args": ["mcp", "serve"]
+    }
+  }
+}

package/src/templates/cursor/rules/gitcontext.mdc

@@ -0,0 +1,25 @@
+---
+description: GitContext integration rules
+globs:
+alwaysApply: true
+---
+
+# GitContext
+
+This repository uses GitContext for AI-assisted knowledge capture.
+
+## Available MCP Tools
+
+Use the `gitcontext` MCP server tools to capture knowledge as you work:
+
+- `capture_doc` — capture a learning, bug, convention, or blocker doc
+- `get_git_context` — get current branch, commit, and recent changes
+- `get_git_diff` — get diff between branches
+- `query_docs` — search existing docs
+
+## When to Capture
+
+- **Bug**: after fixing a non-obvious issue — include root cause and fix
+- **Convention**: after making a design decision or establishing a code pattern
+- **Learning**: after understanding something that will help future work
+- **Blocker**: when hitting a blocking dependency or external issue

package/src/templates/gemini/commands/capture-blocker.md

@@ -0,0 +1,27 @@
+# Capture Blocker
+
+Capture a blocker doc — something that is blocking or has blocked progress on a task or feature.
+
+## Steps
+
+1. Gather context from the current conversation and recent git history:
+   ```bash
+   git log --oneline -10
+   ```
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `blocker`
+   - `title`: concise description of what is blocked (e.g., "Cannot run migrations: DATABASE_URL_DIRECT not set in CI")
+   - `summary`: 2–4 sentences describing what is blocked, why, and current status
+   - `tags`: relevant keywords (e.g., `["ci", "migrations", "env"]`)
+   - `code_snippet` (optional): error output or relevant config
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+@capture-blocker
+@capture-blocker <optional: brief description to seed context>
+```

package/src/templates/gemini/commands/capture-bug.md

@@ -0,0 +1,28 @@
+# Capture Bug
+
+Capture a bug doc — a bug that was found, diagnosed, and fixed (or is being fixed).
+
+## Steps
+
+1. Gather context from the current conversation and recent git history:
+   ```bash
+   git log --oneline -10
+   git diff HEAD~1
+   ```
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `bug`
+   - `title`: concise description of the bug (e.g., "Auth token expiry check uses < instead of <=")
+   - `summary`: 2–4 sentences covering symptom, root cause, and fix
+   - `tags`: relevant keywords (e.g., `["auth", "token", "expiry"]`)
+   - `code_snippet` (optional): the fix or the problematic code
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+@capture-bug
+@capture-bug <optional: brief description to seed context>
+```

package/src/templates/gemini/commands/capture-convention.md

@@ -0,0 +1,24 @@
+# Capture Convention
+
+Capture a convention doc — a decision about how code should be structured, named, or written in this project.
+
+## Steps
+
+1. Gather context from the current conversation and relevant files in the repo.
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `convention`
+   - `title`: concise description of the convention (e.g., "Server functions must be defined in services/, not route files")
+   - `summary`: 2–4 sentences explaining the convention and why it exists
+   - `tags`: relevant keywords (e.g., `["architecture", "server-functions", "tanstack"]`)
+   - `code_snippet` (optional): example of the pattern in practice
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+@capture-convention
+@capture-convention <optional: brief description to seed context>
+```

package/src/templates/gemini/commands/capture-learning.md

@@ -0,0 +1,27 @@
+# Capture Learning
+
+Capture a learning doc — a new insight, technique, or understanding gained during development.
+
+## Steps
+
+1. Gather context from the current conversation and recent git history:
+   ```bash
+   git log --oneline -10
+   ```
+
+2. Use the `gitcontext` MCP server to create the doc:
+   - Tool: `capture_doc`
+   - `type`: `learning`
+   - `title`: concise, specific (e.g., "Vite requires explicit file extensions for dynamic imports")
+   - `summary`: 2–4 sentences explaining the learning clearly
+   - `tags`: relevant keywords (e.g., `["vite", "esm", "bundler"]`)
+   - `code_snippet` (optional): illustrative code if applicable
+
+3. After creating the doc, share the returned link.
+
+## Usage
+
+```
+@capture-learning
+@capture-learning <optional: brief description to seed context>
+```

package/src/templates/gemini/settings.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "gitcontext": {
+      "command": "gitcontext",
+      "args": ["mcp", "serve"]
+    }
+  }
+}

package/src/templates/vscode/copilot-instructions-append.md

@@ -0,0 +1,4 @@
+## GitContext
+
+This repository uses GitContext for AI-assisted knowledge capture.
+Use the `gitcontext` MCP tools (`capture_doc`, `get_git_context`, `query_docs`) to capture learnings, bugs, conventions, and blockers as you work.

package/src/templates/vscode/mcp.json

@@ -0,0 +1,9 @@
+{
+  "servers": {
+    "gitcontext": {
+      "type": "stdio",
+      "command": "gitcontext",
+      "args": ["mcp", "serve"]
+    }
+  }
+}

package/src/templates/windsurf/windsurfrules

@@ -0,0 +1,19 @@
+# GitContext
+
+This repository uses GitContext for AI-assisted knowledge capture.
+
+## Available MCP Tools
+
+Use the `gitcontext` MCP server tools to capture knowledge as you work:
+
+- `capture_doc` — capture a learning, bug, convention, or blocker doc
+- `get_git_context` — get current branch, commit, and recent changes
+- `get_git_diff` — get diff between branches
+- `query_docs` — search existing docs
+
+## When to Capture
+
+- **Bug**: after fixing a non-obvious issue — include root cause and fix
+- **Convention**: after making a design decision or establishing a code pattern
+- **Learning**: after understanding something that will help future work
+- **Blocker**: when hitting a blocking dependency or external issue