taskin 4.2.0 → 4.3.0

package/README.md

@@ -106,7 +106,11 @@ Taskin is built as a modular ecosystem. Besides the CLI, you can use individual
 - `taskin new` - Create a new task (alias: `create`)
 - `taskin start <id>` - Start working on a task (suggests commits)
 - `taskin pause <id>` - Pause work on a task (auto-commits work in progress)
+- `taskin review <id>` - Mark a task as ready for review
 - `taskin finish <id>` - Complete a task (suggests commits)
+
+`new`, `start`, `review` and `finish` each accept `--no-skip-ci`. See
+[The CI-skip tag](#the-ci-skip-tag).
 - `taskin stats [options]` - Show statistics
   - `--user` - User statistics
   - `--team` - Team statistics
@@ -118,8 +122,33 @@ Taskin is built as a modular ecosystem. Besides the CLI, you can use individual
   - `--filter-open` - Show only open tasks
   - `--filter-closed` - Show only closed tasks
 - `taskin mcp-server` - Start MCP server for Claude Desktop integration (alias: `mcp`)
+- `taskin mcp-install` - Register the MCP server in this project's `.mcp.json`
+  - `-f, --force` - Replace an existing `taskin` entry that differs
+  - `--no-probe` - Skip starting the server to verify the entry works
 - `taskin help` - Show help information
 
+### The CI-skip tag
+
+The commits Taskin writes on its own carry a tag so a status change does not
+burn a pipeline run — `[skip ci]` by default, configurable per project as
+`automation.ciSkipTag` in `.taskin.json`. An empty string appends nothing, which
+is how a project asks for CI to run on those commits too.
+
+There is one case the project-wide setting cannot get right. GitHub reads
+**only the head commit of a push**. When you commit your work and then run
+`taskin finish`, the status commit lands on top — and its tag skips the whole
+push, including the release of the work you just finished.
+
+For that push, turn the tag off for the one call:
+
+```bash
+taskin finish 042 --no-skip-ci
+```
+
+The flag only turns the tag off. There is no way to force it on in a project
+that configured an empty string: a project that asked for "CI always" has no use
+for skipping case by case.
+
 ### Automation Levels
 
 Taskin supports three automation levels for git commits:
@@ -138,36 +167,29 @@ Taskin includes an MCP server that allows AI assistants like Claude Desktop to i
 taskin mcp-server
 ```
 
-### Integration with Claude Desktop
-
-Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):
+### Registering it in a project
 
-```json
-{
-  "mcpServers": {
-    "taskin": {
-      "args": ["taskin@beta", "mcp-server"],
-      "command": "npx"
-    }
-  }
-}
+```bash
+taskin mcp-install
 ```
 
-Or if installed globally:
+Writes `.mcp.json` at the **project root** — not wherever you ran it from, which
+matters in a monorepo, where a subdirectory has no lockfile to detect the
+package manager from. It merges with servers already configured there, leaves a
+differing `taskin` entry alone until you pass `--force`, and refuses a malformed
+file instead of destroying it.
 
-```json
-{
-  "mcpServers": {
-    "taskin": {
-      "args": ["mcp-server"],
-      "command": "taskin"
-    }
-  }
-}
-```
+Then it starts the server over stdio and compares the tools it advertises
+against the ones this version offers. Asking only "did it answer?" is not
+enough: the command can resolve to a *different* taskin — an older global
+install answers happily, with the wrong set of tools. Skip the check with
+`--no-probe`.
+
+### Integration with Claude Desktop
 
 **Available MCP Tools:**
 
+- `list_tasks` - List tasks, with optional filters
 - `start_task` - Start working on a task
 - `finish_task` - Mark a task as finished