formatting and linting

Author: mhashim6

bun.lock

@@ -26,12 +26,7 @@ import tsPlugin from '@typescript-eslint/eslint-plugin';
 export default [
   js.configs.recommended,
   {
-    ignores: [
-      'node_modules/**',
-      'dist/**',
-      'coverage/**',
-      'src/store/migrations-data.ts',
-    ],
+    ignores: ['node_modules/**', 'dist/**', 'coverage/**', 'src/store/migrations-data.ts'],
   },
   {
     files: ['**/*.ts'],

eslint.config.js

@@ -0,0 +1,10 @@
+pre-commit:
+  parallel: true
+  jobs:
+    - name: lint
+      glob: '*.{ts,js}'
+      run: bunx eslint {staged_files}
+
+    - name: format
+      glob: '*.{ts,js,json,md,yml,yaml,sql}'
+      run: bunx prettier --check {staged_files}

lefthook.yml

@@ -49,6 +49,7 @@
     "@typescript-eslint/parser": "^8.58.1",
     "eslint": "^9.39.4",
     "eslint-plugin-import": "^2.32.0",
+    "lefthook": "^2.1.6",
     "prettier": "^3.8.2",
     "typescript": "^6.0.2"
   }

package.json

@@ -6,12 +6,12 @@ validate decisions as first-class MCP tools.
 
 ## What it does
 
-| Feature | How |
-|---|---|
-| **Decisions in context** | Session-start hook injects the Kauri projection (pinned + index) into Claude's context automatically |
-| **MCP tools** | Claude sees `kauri_record`, `kauri_query`, `kauri_show`, etc. alongside Bash/Read/Edit |
-| **Skills** | `/kauri:record-decision` and `/kauri:check-staleness` teach Claude when and how to use Kauri |
-| **Post-commit staleness** | After `git commit`, a hook checks for stale decisions and alerts Claude |
+| Feature                   | How                                                                                                  |
+| ------------------------- | ---------------------------------------------------------------------------------------------------- |
+| **Decisions in context**  | Session-start hook injects the Kauri projection (pinned + index) into Claude's context automatically |
+| **MCP tools**             | Claude sees `kauri_record`, `kauri_query`, `kauri_show`, etc. alongside Bash/Read/Edit               |
+| **Skills**                | `/kauri:record-decision` and `/kauri:check-staleness` teach Claude when and how to use Kauri         |
+| **Post-commit staleness** | After `git commit`, a hook checks for stale decisions and alerts Claude                              |
 
 ## Prerequisites
 
@@ -75,30 +75,33 @@ automatically and exposes all 12 Kauri tools:
 
 ### Hooks
 
-| Event | Trigger | Action |
-|---|---|---|
-| `SessionStart` (startup) | New session begins | Injects decision projection into context |
+| Event                    | Trigger              | Action                                                |
+| ------------------------ | -------------------- | ----------------------------------------------------- |
+| `SessionStart` (startup) | New session begins   | Injects decision projection into context              |
 | `SessionStart` (compact) | Context is compacted | Re-injects projection so decisions survive compaction |
-| `PostToolUse` (Bash) | After a `git commit` | Runs staleness check, alerts if records are stale |
+| `PostToolUse` (Bash)     | After a `git commit` | Runs staleness check, alerts if records are stale     |
 
 ### Skills
 
-| Skill | Invocation | Purpose |
-|---|---|---|
+| Skill           | Invocation                       | Purpose                                      |
+| --------------- | -------------------------------- | -------------------------------------------- |
 | record-decision | `/kauri:record-decision [title]` | Guided workflow for recording a new decision |
-| check-staleness | `/kauri:check-staleness` | Review and resolve stale decisions |
+| check-staleness | `/kauri:check-staleness`         | Review and resolve stale decisions           |
 
 ## Troubleshooting
 
 **"kauri: command not found"** — The `kauri` binary isn't in PATH. Either:
+
 - Run `bun run build` in the Kauri repo and add `dist/` to your PATH
 - Or use `bun run /path/to/kauri/src/cli.ts` and update `.mcp.json` accordingly
 
 **No decisions showing at session start** — Make sure you've run `kauri init`
 in your project directory and have at least one recorded decision.
 
 **MCP tools not appearing** — Check that the plugin is loaded:
+
 ```
 /reload-plugins
 ```
+
 Then verify with `/kauri:check-staleness` — if the skill loads, the plugin is active.

plugins/claude-code/README.md

@@ -4,7 +4,7 @@ description: Check if recorded Kauri decisions are stale. Use when assessing cod
 disable-model-invocation: false
 user-invocable: true
 allowed-tools: mcp__kauri__kauri_check mcp__kauri__kauri_show mcp__kauri__kauri_validate
-argument-hint: ""
+argument-hint: ''
 ---
 
 # Check Decision Staleness
@@ -28,6 +28,7 @@ Run a staleness check on all active Kauri decisions and help the user resolve an
 ## What "stale" means
 
 A record is stale when:
+
 - **Time-based**: More than `ttl_days` have passed since last validation (default 90 days).
 - **File-based**: A file associated with the record has changed content since the last validation.
 

plugins/claude-code/skills/check-staleness/SKILL.md

@@ -4,7 +4,7 @@ description: Consult existing Kauri decisions before planning or implementing ch
 disable-model-invocation: false
 user-invocable: true
 allowed-tools: mcp__kauri__kauri_query mcp__kauri__kauri_show mcp__kauri__kauri_taxonomy_list
-argument-hint: "[topic or file path]"
+argument-hint: '[topic or file path]'
 ---
 
 # Consult Existing Decisions

plugins/claude-code/skills/consult/SKILL.md

@@ -4,7 +4,7 @@ description: Draft a Kauri decision for human review before recording it. This s
 disable-model-invocation: false
 user-invocable: true
 allowed-tools: mcp__kauri__kauri_taxonomy_list mcp__kauri__kauri_query mcp__kauri__kauri_record
-argument-hint: "[topic of the decision]"
+argument-hint: '[topic of the decision]'
 ---
 
 # Propose a Decision
@@ -52,6 +52,7 @@ poorly-worded records from accumulating.
 ## Quality guidelines
 
 A good decision record:
+
 - **Title**: One sentence, starts with a verb or states the choice clearly.
   Good: "Use JWT with 15-minute refresh tokens". Bad: "Auth stuff".
 - **Body**: Explains WHY, not just WHAT. Includes the trade-off or
@@ -67,4 +68,4 @@ A good decision record:
 
 - Trivial choices (variable naming, import order)
 - Temporary workarounds with a known fix date
-- Facts or observations — decisions are *choices with rationale*
+- Facts or observations — decisions are _choices with rationale_

plugins/claude-code/skills/propose/SKILL.md

@@ -4,7 +4,7 @@ description: Record a project decision using Kauri. Use when you've chosen an ar
 disable-model-invocation: false
 user-invocable: true
 allowed-tools: mcp__kauri__kauri_record mcp__kauri__kauri_taxonomy_list mcp__kauri__kauri_query
-argument-hint: "[title of the decision]"
+argument-hint: '[title of the decision]'
 ---
 
 # Record a Decision
@@ -19,6 +19,7 @@ You are recording a project decision using Kauri. The decision should be a delib
 ## Recording the decision
 
 Use `kauri_record` with:
+
 - **title**: A short, scannable title (the user provided: "$ARGUMENTS")
 - **body**: The full rationale in markdown. Include:
   - What was decided
@@ -33,7 +34,7 @@ Use `kauri_record` with:
 
 - Trivial implementation details (variable names, formatting)
 - Temporary workarounds intended to be removed immediately
-- Facts or observations (decisions are *choices*, not notes)
+- Facts or observations (decisions are _choices_, not notes)
 
 ## After recording
 

plugins/claude-code/skills/record-decision/SKILL.md

@@ -4,7 +4,7 @@ description: Review recent code changes against Kauri decisions. Use after imple
 disable-model-invocation: false
 user-invocable: true
 allowed-tools: Bash(git diff *) Bash(git log *) mcp__kauri__kauri_query mcp__kauri__kauri_show mcp__kauri__kauri_validate Read
-argument-hint: "[file or commit range]"
+argument-hint: '[file or commit range]'
 ---
 
 # Review Changes Against Decisions