mini-coder 0.1.1 → 0.1.2

package/docs/mini-coder.1.md

@@ -86,7 +86,7 @@ Developer-focused CLI coding agent. Prioritizes dev flow — no slow startup, no
 : Remove MCP server.
 
 `/agent` \[*name*\]
-: Set or clear active primary agent.
+: Set or clear active agent.
 
 `/review`
 : Review changes (custom command, auto-created globally).
@@ -119,9 +119,6 @@ Developer-focused CLI coding agent. Prioritizes dev flow — no slow startup, no
 **shell**
 : Execute bash commands; repo inspection and `mc-edit` edits happen here.
 
-**subagent**
-: Spawn a focused mini-agent for parallel subtasks.
-
 **listSkills**
 : List discovered skills (metadata only).
 
@@ -165,16 +162,7 @@ Drop a `.md` file in `.agents/commands/` (local) or `~/.agents/commands/` (globa
 : Shown in `/help`.
 
 `model`
-: Override model (only with `context: fork`).
-
-`context`
-: `fork` to run as isolated subagent; default is inline.
-
-`subtask`
-: `true` forces subagent (OpenCode-compatible alias).
-
-`agent`
-: Run under named agent's system prompt (only with `context: fork`).
+: Optional metadata field.
 
 **Argument substitution:**
 
@@ -198,12 +186,9 @@ Drop a `.md` file in `.agents/agents/` (local) or `~/.agents/agents/` (global).
 : Shown in `/help`.
 
 `model`
-: Override active model.
-
-`mode`
-: `primary` excludes from subagent tool; `subagent`/`all`/omitted keeps it available.
+: Optional metadata field.
 
-Body is the agent system prompt. Non-primary agents are exposed to the **subagent** tool for delegation.
+Body is the agent system prompt.
 
 ## SKILLS
 

package/lefthook.yml

@@ -0,0 +1,15 @@
+pre-commit:
+  parallel: true
+  commands:
+    jscpd:
+      run: bun run jscpd
+    knip:
+      run: bun run knip
+    typecheck:
+      run: bun run typecheck
+    format:
+      run: bun run format
+    lint:
+      run: bun run lint
+    test:
+      run: bun run test

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "mini-coder",
-	"version": "0.1.1",
+	"version": "0.1.2",
 	"description": "A small, fast CLI coding agent",
 	"module": "src/index.ts",
 	"type": "module",
@@ -18,7 +18,7 @@
 		"test": "bun test --only-failures",
 		"test:verbose": "bun test",
 		"jscpd": "jscpd src",
-		"ui-oneshot": "bun scripts/ui-oneshot.ts"
+		"prepare": "lefthook install"
 	},
 	"dependencies": {
 		"@ai-sdk/anthropic": "^3.0.60",
@@ -37,6 +37,7 @@
 		"@types/bun": "latest",
 		"jscpd": "^4.0.8",
 		"knip": "^5.86.0",
+		"lefthook": "^2.1.4",
 		"typescript": "^5.9.3"
 	},
 	"knip": {

package/research.md

@@ -1,38 +0,0 @@
-I want your help exploring how could we use yoctocolor to add color ouput to commonly used shell commands. Let's first check the db, check the recent past sessions for a sample. Then check for the shell usage and assert the most common commands
-
-Response:
-
-## Shell Usage Analysis (from 101 sessions)
-
-Most common commands:
-| Command | Count | Opportunity |
-|---------|-------|-------------|
-| `cat` | 72 | File content preview |
-| `git` | 54 | Status/diff output |
-| `bun` | 32 | Test/build output |
-| `sed` | 29 | Transform preview |
-| `mc-edit` | 26 | File edits |
-| `nl` | 12 | Line numbers |
-| `rg` | 11 | Search matches |
-| `npm` | 9 | Package output |
-| `grep` | 7 | Match highlighting |
-| `ls` | 5 | File listings |
-
-## Current Shell Output Coloring (in `tool-result-renderers.ts`)
-
-The shell result renderer already uses yoctocolors:
-
-- **Status badges**: `c.green("done")` / `c.red("error")` / `c.yellow("timeout")`
-- **Stderr lines**: `c.red()` for error emphasis
-- **Stdout/stderr line separators**: `c.dim()` or colored pipe character
-
-## Enhancement Opportunities
-
-1. **Command syntax highlighting** - Color `git`, `bun`, `npm` commands differently in the tool call line
-2. **File path highlighting** - Use `c.cyan()` for paths in output
-3. **Git diffs from mc-edit** - Render a colored diff
-4. **Line numbers** - `nl` output could use `c.yellow()` for numbers
-5. **Git output** - Branch names in `c.cyan()`, commit hashes in `c.yellow()`, file statuses (M/A/D) in color
-6. **rg/grep matches** - Highlight matching text in `c.greenBright()` or `c.yellow()`
-7. **Exit code** - Non-zero codes in `c.red()` or `c.yellow()`
-8. **Test output** - `bun test` results: passes in `c.green()`, fails in `c.red()`, skips in `c.yellow()`