mini-coder 0.1.0 → 0.1.2

package/docs/custom-commands.md

@@ -1,141 +0,0 @@
-# Custom Commands
-
-Custom commands let you define reusable prompts that run as `/command` in the mini-coder REPL.
-
-mini-coder is shell-first: when a command needs repo inspection or verification, tell it to use shell. When it needs a targeted file edit, tell it to invoke `mc-edit` from shell rather than relying on old local file-edit tools.
-
-## Where to put them
-
-| Location | Scope |
-|---|---|
-| `.agents/commands/*.md` | Current repo only |
-| `~/.agents/commands/*.md` | All projects (global) |
-| `.claude/commands/*.md` | Current repo only (Claude-compatible) |
-| `~/.claude/commands/*.md` | All projects (global, Claude-compatible) |
-
-Local commands override global ones with the same name. At the same scope, `.agents` wins over `.claude`.
-
-## Create a command
-
-Create a markdown file. The filename becomes the command name.
-
-`.agents/commands/standup.md`:
-
-```md
----
-description: Summarise what changed since yesterday
-model: zen/claude-haiku-4-5
----
-
-Run `!`git log --oneline --since=yesterday`` and summarise the changes
-as a short standup update. Group by theme, skip merge commits.
-```
-
-Then in the REPL:
-
-```
-/standup
-```
-
-## Frontmatter fields
-
-| Field | Required | Description |
-|---|---|---|
-| `description` | No | Shown in `/help`. Defaults to the command name. |
-| `model` | No | Override the active model for this command (only applies when `context: fork`). |
-| `context` | No | Set to `fork` to run the command as an isolated subagent; default runs inline. |
-| `subtask` | No | Set to `true` to force subagent execution (OpenCode-compatible alias for `context: fork`). |
-| `agent` | No | Run the command under a named agent's system prompt (only applies when `context: fork`). |
-
-## Arguments
-
-Use `$ARGUMENTS` for the full argument string, or `$1`, `$2`, … `$9` for individual tokens.
-
-`.agents/commands/search.md`:
-
-```md
----
-description: Search the codebase for a topic
-model: zen/claude-haiku-4-5
----
-
-Search the codebase for: $ARGUMENTS
-
-Use shell and skill-loading tools as needed to explore thoroughly. Report all
-relevant files, key code snippets with line numbers, and a short summary.
-Be exhaustive but concise. No edits.
-```
-
-```
-/search session management
-/search error handling in providers
-```
-
-Positional tokens:
-
-```md
----
-description: Create a new component
----
-
-Create a React component named $1 in the $2 directory.
-Use TypeScript, include prop types and a default export.
-```
-
-```
-/component Button src/ui
-```
-
-## Shell interpolation
-
-Use `` !`cmd` `` to inject shell output into the prompt at expansion time.
-Commands time out after 10 seconds.
-
-```md
----
-description: Review failing tests
----
-
-The following tests are currently failing:
-
-!`bun test 2>&1 | grep "fail\|✗" | head -20`
-
-Investigate the failures and suggest fixes. Read the relevant source
-files before drawing conclusions.
-```
-
-```
-/fix-tests
-```
-
-## Model override
-
-Specify a model in frontmatter to use a faster or cheaper model for
-lightweight tasks regardless of what the session is currently set to.
-
-```md
----
-description: Quick symbol search
-model: zen/claude-haiku-4-5
----
-
-Find all usages of $ARGUMENTS across the codebase using shell.
-List each occurrence with file path and line number. No explanations needed.
-```
-
-Large models for deep analysis, small models for search and lookup.
-
-## Precedence
-
-Custom commands shadow built-ins. The global `/review`
-command (auto-created at `~/.agents/commands/review.md` on first run) works
-the same way — a local `.agents/commands/review.md` will override it.
-
-## Listing commands
-
-```
-/help
-```
-
-Custom commands are listed at the bottom under **custom commands**, tagged
-with `(local)` or `(global)`.

package/docs/skills.md

@@ -1,83 +0,0 @@
-# Skills
-
-Skills are reusable instruction files discovered automatically from local and global directories.
-
-When a skill tells mini-coder how to work with files, prefer shell for inspection/search/verification and `mc-edit` from shell for targeted edits.
-
-- The model sees **skill metadata only** by default (name, description, source).
-- Full `SKILL.md` content is loaded **on demand**:
-	- when explicitly requested with the runtime skill tools (`listSkills` / `readSkill`), or
-	- when you reference `@skill-name` in your prompt.
-
-## Discovery locations
-
-Skills live in folders containing `SKILL.md`:
-
-| Location | Scope |
-|---|---|
-| `.agents/skills/<name>/SKILL.md` | Local |
-| `.claude/skills/<name>/SKILL.md` | Local (Claude-compatible) |
-| `~/.agents/skills/<name>/SKILL.md` | Global |
-| `~/.claude/skills/<name>/SKILL.md` | Global (Claude-compatible) |
-
-Local discovery walks up from the current working directory to the git worktree root.
-
-## Precedence rules
-
-If multiple skills share the same `name`, precedence is deterministic:
-
-1. Nearest local directory wins over farther ancestor directories.
-2. Any local skill wins over global.
-3. At the same scope/path level, `.agents` wins over `.claude`.
-
-## Frontmatter
-
-`SKILL.md` frontmatter supports:
-
-- `name` (**required**)
-- `description` (**required**)
-
-`name` constraints:
-
-- lowercase alphanumeric and hyphen format (`^[a-z0-9]+(?:-[a-z0-9]+)*$`)
-- 1–64 characters
-
-Unknown frontmatter fields are allowed.
-
-If either `name` or `description` is missing, mini-coder skips the skill and prints a warning.
-
-
-## Create a skill
-
-`.agents/skills/conventional-commits/SKILL.md`:
-
-```md
----
-name: conventional-commits
-description: Conventional commit message format rules
----
-
-# Conventional Commits
-
-Use:
-<type>(<scope>): <short summary>
-```
-
-## Use a skill explicitly
-
-```text
-@conventional-commits write a commit message for my staged changes
-```
-
-`@skill-name` injects the raw skill body wrapped as:
-
-```xml
-<skill name="conventional-commits">
-...
-</skill>
-```
-
-## Tab completion and help
-
-- Type `@` then `Tab` to complete skill names.
-- Run `/help` to list discovered skills with `(local)` / `(global)` tags.

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()`