mcp-coder-utils 0.1.4__tar.gz → 0.1.6__tar.gz

mcp_coder_utils-0.1.6/.claude/CLAUDE.md

@@ -0,0 +1,102 @@
+## About this repo
+
+`mcp-coder-utils` is a **leaf library**: shared low-level Python helpers (subprocess, logging, fs) used by `mcp-coder`, `mcp-tools-py`, `mcp-workspace`, and `mcp-tools-sql`.
+
+**Architectural rules:**
+
+- Pure Python, language-agnostic. No ecosystem knowledge (no `pyproject.toml` parsing, no venv, no `.csproj`, no SQL).
+- Zero internal dependencies. Stdlib + pinned third-party libs only.
+- Every public function must have ≥2 real consumers. Single-user helpers stay in the consumer.
+- Public API is stable. Renames and signature changes break every downstream repo.
+
+When in doubt, keep it in the consumer until a second consumer needs it.
+
+## MCP Tools — mandatory
+
+**Do NOT use native Claude Code file tools** (`Read`, `Write`, `Edit`, `Glob`, `Grep`, `Bash`) for any operation that has an MCP equivalent. Always use the `mcp__mcp-workspace__*` tools instead. This applies to all file reading, writing, editing, searching, listing, and git operations.
+
+### Tool mapping
+
+| Task | MCP tool |
+|------|----------|
+| Read file | `mcp__mcp-workspace__read_file` |
+| Edit file | `mcp__mcp-workspace__edit_file` |
+| Write file | `mcp__mcp-workspace__save_file` |
+| Append to file | `mcp__mcp-workspace__append_file` |
+| Delete file | `mcp__mcp-workspace__delete_this_file` |
+| Move file | `mcp__mcp-workspace__move_file` |
+| List directory | `mcp__mcp-workspace__list_directory` |
+| Search files | `mcp__mcp-workspace__search_files` |
+| Search reference files | `mcp__mcp-workspace__search_reference_files` |
+| Read reference project | `mcp__mcp-workspace__read_reference_file` |
+| List reference dir | `mcp__mcp-workspace__list_reference_directory` |
+| Get reference projects | `mcp__mcp-workspace__get_reference_projects` |
+| Run pytest | `mcp__mcp-tools-py__run_pytest_check` |
+| Run pylint | `mcp__mcp-tools-py__run_pylint_check` |
+| Run mypy | `mcp__mcp-tools-py__run_mypy_check` |
+| Run lint-imports | `mcp__mcp-tools-py__run_lint_imports_check` |
+| Run vulture | `mcp__mcp-tools-py__run_vulture_check` |
+| Format code (black+isort) | `mcp__mcp-tools-py__run_format_code` |
+| Get library source | `mcp__mcp-tools-py__get_library_source` |
+| Refactoring | `mcp__mcp-tools-py__move_symbol`, `move_module`, `rename_symbol`, `list_symbols`, `find_references` |
+| Git (read-only) | `mcp__mcp-workspace__git` |
+| Get base branch | `mcp__mcp-workspace__get_base_branch` |
+| Check file size | `mcp__mcp-workspace__check_file_size` |
+| Check branch status | `mcp__mcp-workspace__check_branch_status` |
+| List GitHub issues | `mcp__mcp-workspace__github_issue_list` |
+| View GitHub issue | `mcp__mcp-workspace__github_issue_view` |
+| View GitHub PR | `mcp__mcp-workspace__github_pr_view` |
+| Search GitHub | `mcp__mcp-workspace__github_search` |
+
+### Reference projects
+
+Read-only browse via `mcp__mcp-workspace__read_reference_file`:
+
+- `mcp_coder` — `mcp_coder` source
+- `mcp-workspace` — `mcp-workspace` source
+- `mcp-config` — `mcp-config` source
+- `mcp-tools-py` — `mcp-tools-py` source
+
+## Code quality checks
+
+After making code changes, run:
+
+```
+mcp__mcp-tools-py__run_pylint_check
+mcp__mcp-tools-py__run_pytest_check
+mcp__mcp-tools-py__run_mypy_check
+```
+
+All checks must pass before proceeding.
+
+**Pytest:** always use `extra_args: ["-n", "auto"]` for parallel execution. No integration test markers — run everything.
+
+## Git operations
+
+**Prefer MCP tools** for read-only git operations: use `mcp__mcp-workspace__git` with the `command` parameter (log, diff, status, merge_base, show, branch, fetch, rev_parse, ls_tree, ls_files, ls_remote). These run without permission prompts.
+
+**Compact diff:** `mcp__mcp-workspace__git` with command `"diff"` includes compact diff by default — detects moved code, collapses unchanged blocks. Use `compact=False` for raw output.
+
+**Bash commands** for git operations that have no MCP equivalent:
+
+```
+git commit / git add
+mcp-coder gh-tool set-status <label>  # change issue workflow status label
+```
+
+**Status labels:** use `mcp-coder gh-tool set-status` to change issue workflow status — never use raw `gh issue edit` with label flags.
+
+**Before every commit:** run `mcp__mcp-tools-py__run_format_code`, then stage and commit.
+
+**Bash discipline:** no `cd` prefix. Don't chain approved with unapproved commands. Run them separately.
+
+**Commit messages:** standard format, clear and descriptive. No attribution footers.
+
+## Writing style
+
+Be concise. If one line works, don't use three.
+
+## Asking questions
+
+Never use the AskUserQuestion tool. Ask questions as plain text in the chat.
+

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/knowledge_base/refactoring_principles.md

@@ -15,7 +15,7 @@ Quick reference for refactoring rules and tools. For detailed process, examples,
 1. Plan target structure
 2. Move source code — `move_symbol` / `move_module`
 3. Move tests to mirror new structure
-4. Review diff — `mcp__workspace__git_diff` (remaining diff should be imports only)
+4. Review diff — `mcp__mcp-workspace__git_diff` (remaining diff should be imports only)
 5. Run all checks — pytest, pylint, mypy, ruff
 6. Check file sizes — `mcp-coder check file-size --max-lines 750`
 

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/settings.local.json

@@ -39,44 +39,44 @@
       "mcp__obsidian-wiki__remove-tags",
       "mcp__obsidian-wiki__rename-tag",
       "mcp__obsidian-wiki__search-vault",
-      "mcp__tools-py__find_references",
-      "mcp__tools-py__get_library_source",
-      "mcp__tools-py__list_symbols",
-      "mcp__tools-py__move_module",
-      "mcp__tools-py__move_symbol",
-      "mcp__tools-py__rename_symbol",
-      "mcp__tools-py__run_format_code",
-      "mcp__tools-py__run_lint_imports_check",
-      "mcp__tools-py__run_mypy_check",
-      "mcp__tools-py__run_pylint_check",
-      "mcp__tools-py__run_pytest_check",
-      "mcp__tools-py__run_ruff_check",
-      "mcp__tools-py__run_vulture_check",
-      "mcp__workspace__append_file",
-      "mcp__workspace__check_branch_status",
-      "mcp__workspace__check_file_size",
-      "mcp__workspace__delete_this_file",
-      "mcp__workspace__edit_file",
-      "mcp__workspace__get_base_branch",
-      "mcp__workspace__get_reference_projects",
-      "mcp__workspace__git",
-      "mcp__workspace__github_issue_list",
-      "mcp__workspace__github_issue_view",
-      "mcp__workspace__github_pr_view",
-      "mcp__workspace__github_search",
-      "mcp__workspace__list_directory",
-      "mcp__workspace__list_reference_directory",
-      "mcp__workspace__move_file",
-      "mcp__workspace__read_file",
-      "mcp__workspace__read_reference_file",
-      "mcp__workspace__save_file",
-      "mcp__workspace__search_files",
-      "mcp__workspace__search_reference_files"
+      "mcp__mcp-tools-py__find_references",
+      "mcp__mcp-tools-py__get_library_source",
+      "mcp__mcp-tools-py__list_symbols",
+      "mcp__mcp-tools-py__move_module",
+      "mcp__mcp-tools-py__move_symbol",
+      "mcp__mcp-tools-py__rename_symbol",
+      "mcp__mcp-tools-py__run_format_code",
+      "mcp__mcp-tools-py__run_lint_imports_check",
+      "mcp__mcp-tools-py__run_mypy_check",
+      "mcp__mcp-tools-py__run_pylint_check",
+      "mcp__mcp-tools-py__run_pytest_check",
+      "mcp__mcp-tools-py__run_ruff_check",
+      "mcp__mcp-tools-py__run_vulture_check",
+      "mcp__mcp-workspace__append_file",
+      "mcp__mcp-workspace__check_branch_status",
+      "mcp__mcp-workspace__check_file_size",
+      "mcp__mcp-workspace__delete_this_file",
+      "mcp__mcp-workspace__edit_file",
+      "mcp__mcp-workspace__get_base_branch",
+      "mcp__mcp-workspace__get_reference_projects",
+      "mcp__mcp-workspace__git",
+      "mcp__mcp-workspace__github_issue_list",
+      "mcp__mcp-workspace__github_issue_view",
+      "mcp__mcp-workspace__github_pr_view",
+      "mcp__mcp-workspace__github_search",
+      "mcp__mcp-workspace__list_directory",
+      "mcp__mcp-workspace__list_reference_directory",
+      "mcp__mcp-workspace__move_file",
+      "mcp__mcp-workspace__read_file",
+      "mcp__mcp-workspace__read_reference_file",
+      "mcp__mcp-workspace__save_file",
+      "mcp__mcp-workspace__search_files",
+      "mcp__mcp-workspace__search_reference_files"
     ]
   },
   "enableAllProjectMcpServers": true,
   "enabledMcpjsonServers": [
-    "tools-py",
-    "workspace"
+    "mcp-tools-py",
+    "mcp-workspace"
   ]
 }

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/check_branch_status/SKILL.md

@@ -1,6 +1,5 @@
 ---
 description: Check branch readiness including CI, rebase needs, tasks, and labels
-disable-model-invocation: true
 allowed-tools:
   - "Bash(mcp-coder check branch-status *)"
 ---

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/commit_push/SKILL.md

@@ -2,14 +2,14 @@
 description: Format code, review changes, commit, and push to remote
 disable-model-invocation: true
 allowed-tools:
-  - mcp__workspace__git
+  - mcp__mcp-workspace__git
   - "Bash(git add *)"
   - "Bash(git commit *)"
   - "Bash(git push *)"
-  - mcp__tools-py__run_format_code
-  - mcp__workspace__read_file
-  - mcp__workspace__list_directory
-  - mcp__workspace__search_files
+  - mcp__mcp-tools-py__run_format_code
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__list_directory
+  - mcp__mcp-workspace__search_files
 ---
 
 # Commit and Push Changes
@@ -17,11 +17,11 @@ allowed-tools:
 Follow this process to commit and push your changes:
 
 ## 1. Format Code
-Use `mcp__tools-py__run_format_code` to format all code (black + isort).
+Use `mcp__mcp-tools-py__run_format_code` to format all code (black + isort).
 
 ## 2. Review Changes
-Use `mcp__workspace__git` with command `"status"` to check working directory state.
-Use `mcp__workspace__git` with command `"diff"` to review the changes.
+Use `mcp__mcp-workspace__git` with command `"status"` to check working directory state.
+Use `mcp__mcp-workspace__git` with command `"diff"` to review the changes.
 
 ## 3. Stage Changes
 Stage all relevant changes (exclude any files that shouldn't be committed).

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/implement_direct/SKILL.md

@@ -3,10 +3,10 @@ name: implement-direct
 disable-model-invocation: true
 argument-hint: [issue-number]
 allowed-tools:
-  - mcp__workspace__github_issue_view
+  - mcp__mcp-workspace__github_issue_view
   - "Bash(mcp-coder gh-tool *)"
-  - mcp__workspace__read_file
-  - mcp__tools-py__run_format_code
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-tools-py__run_format_code
 ---
 
 # Implement Direct
@@ -23,7 +23,7 @@ If no issue number is provided:
 ## Steps
 
 1. **Fetch issue details**
-   Use `mcp__workspace__github_issue_view` to fetch the issue details.
+   Use `mcp__mcp-workspace__github_issue_view` to fetch the issue details.
    Read the issue title, description, and acceptance criteria carefully.
 
 2. **Checkout/create issue branch**
@@ -42,13 +42,13 @@ If no issue number is provided:
    - Keep changes focused and minimal — only what the issue requires
 
 5. **Run quality checks**
-   - `mcp__tools-py__run_pylint_check` — fix all issues
-   - `mcp__tools-py__run_pytest_check` (with `extra_args: ["-n", "auto"]`) — fix all failures
-   - `mcp__tools-py__run_mypy_check` — fix all issues
+   - `mcp__mcp-tools-py__run_pylint_check` — fix all issues
+   - `mcp__mcp-tools-py__run_pytest_check` (with `extra_args: ["-n", "auto"]`) — fix all failures
+   - `mcp__mcp-tools-py__run_mypy_check` — fix all issues
    - `./tools/ruff_check.sh` — fix all issues
 
 6. **Format code**
-   Use `mcp__tools-py__run_format_code` to format all code (black + isort).
+   Use `mcp__mcp-tools-py__run_format_code` to format all code (black + isort).
 
 7. **Update issue status**
    ```bash

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/implementation_new_tasks/SKILL.md

@@ -2,10 +2,10 @@
 description: Create additional implementation steps after code review findings
 disable-model-invocation: true
 allowed-tools:
-  - mcp__workspace__read_file
-  - mcp__workspace__save_file
-  - mcp__workspace__edit_file
-  - mcp__workspace__list_directory
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__save_file
+  - mcp__mcp-workspace__edit_file
+  - mcp__mcp-workspace__list_directory
 ---
 
 # Create Further Implementation Tasks

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/implementation_review/SKILL.md

@@ -1,20 +1,19 @@
 ---
 description: Code review of implementation with compact diff analysis
-disable-model-invocation: true
 allowed-tools:
-  - mcp__workspace__git
-  - mcp__workspace__check_branch_status
-  - mcp__workspace__read_file
-  - mcp__workspace__list_directory
-  - mcp__workspace__search_files
+  - mcp__mcp-workspace__git
+  - mcp__mcp-workspace__check_branch_status
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__list_directory
+  - mcp__mcp-workspace__search_files
 ---
 
 # Implementation Review (Code Review)
 
 **First, ensure we're up to date:**
-Call `mcp__workspace__git` with command `"fetch"` and args `["origin"]`.
-Use `mcp__workspace__git` with command `"status"` to check working directory state.
-Call `mcp__workspace__check_branch_status`.
+Call `mcp__mcp-workspace__git` with command `"fetch"` and args `["origin"]`.
+Use `mcp__mcp-workspace__git` with command `"status"` to check working directory state.
+Call `mcp__mcp-workspace__check_branch_status`.
 
 Confirm and display the current feature branch name.
 
@@ -24,7 +23,7 @@ Confirm and display the current feature branch name.
 
 ## Code Review Request
 
-Use `mcp__workspace__git` with command `"diff"` to get the changes to review.
+Use `mcp__mcp-workspace__git` with command `"diff"` to get the changes to review.
 
 No need to run all checks; do not use pylint warnings. Feel free to further analyse any mentioned files and/or the file structure.
 

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/implementation_review_supervisor/SKILL.md

@@ -2,16 +2,16 @@
 description: Autonomous code review — supervisor delegates to engineer subagents with knowledge base
 disable-model-invocation: true
 allowed-tools:
-  - mcp__workspace__github_issue_view
-  - mcp__workspace__check_branch_status
-  - mcp__workspace__git
-  - mcp__workspace__read_file
-  - mcp__workspace__save_file
-  - mcp__workspace__edit_file
-  - mcp__workspace__list_directory
-  - mcp__tools-py__run_pylint_check
-  - mcp__tools-py__run_pytest_check
-  - mcp__tools-py__run_mypy_check
+  - mcp__mcp-workspace__github_issue_view
+  - mcp__mcp-workspace__check_branch_status
+  - mcp__mcp-workspace__git
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__save_file
+  - mcp__mcp-workspace__edit_file
+  - mcp__mcp-workspace__list_directory
+  - mcp__mcp-tools-py__run_pylint_check
+  - mcp__mcp-tools-py__run_pytest_check
+  - mcp__mcp-tools-py__run_mypy_check
 ---
 
 # Automated Implementation Review (Code Review) / using a supervisor agent
@@ -20,7 +20,7 @@ You are a technical lead supervising a software engineer (subagent). You do not
 
 **Setup:**
 
-1. Read the GitHub issue (call `mcp__workspace__github_issue_view` with the issue number from the branch name), `pr_info/steps/summary.md`, and `pr_info/steps/Decisions.md` (if it exists) to understand requirements and design decisions.
+1. Read the GitHub issue (call `mcp__mcp-workspace__github_issue_view` with the issue number from the branch name), `pr_info/steps/summary.md`, and `pr_info/steps/Decisions.md` (if it exists) to understand requirements and design decisions.
 2. Read the knowledge base files:
    - `.claude/knowledge_base/software_engineering_principles.md`
    - `.claude/knowledge_base/python.md`
@@ -70,6 +70,6 @@ You are a technical lead supervising a software engineer (subagent). You do not
 **Status**: {committed / no changes needed}
 ```
 
-**Subagent instructions:** Remind subagents to follow CLAUDE.md (MCP tools, no `cd` prefix, approved commands only).
+**Subagent instructions:** When launching subagents, instruct them to follow CLAUDE.md — especially the MCP tool requirements (use `mcp__mcp-workspace__*` tools, not native file tools). Also remind them: no `cd` prefix, approved commands only.
 
 **Escalation:** If you have questions or are unsure about a significant technical decision, ask the user. For borderline Accept/Skip findings, default to better code quality rather than asking — only escalate when the fix has meaningful scope or risk, not for trivial changes in either direction.

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/issue_analyse/SKILL.md

@@ -3,10 +3,10 @@ description: Analyse GitHub issue requirements, feasibility, and implementation
 disable-model-invocation: true
 argument-hint: "<issue-number>"
 allowed-tools:
-  - mcp__workspace__github_issue_view
-  - mcp__workspace__git
-  - mcp__workspace__read_file
-  - mcp__workspace__list_directory
+  - mcp__mcp-workspace__github_issue_view
+  - mcp__mcp-workspace__git
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__list_directory
 ---
 
 # Analyse GitHub Issue
@@ -20,7 +20,7 @@ If no issue number is provided:
 1. Read `.vscodeclaude_status.txt` and extract the issue number from the `Issue #NNN` line
 2. If the file doesn't exist or has no issue number, ask the user
 
-Fetch the issue using `mcp__workspace__github_issue_view`.
+Fetch the issue using `mcp__mcp-workspace__github_issue_view`.
 
 ## Instructions
 
@@ -43,7 +43,7 @@ During the discussion, actively identify constraints and rationale — the "why"
 **Base Branch Handling:**
 If the issue contains a `### Base Branch` section:
 - Display the specified base branch prominently
-- Verify the branch exists using `mcp__workspace__git` with command `"ls_remote"` and args `["--heads", "origin", "<branch-name>"]`
+- Verify the branch exists using `mcp__mcp-workspace__git` with command `"ls_remote"` and args `["--heads", "origin", "<branch-name>"]`
 - If the branch does NOT exist, show a clear warning:
   "Warning: Base branch 'X' does not exist on remote. Branch creation will fail."
 - Continue with the analysis (non-blocking error)

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/issue_approve/SKILL.md

@@ -3,10 +3,10 @@ description: Approve issue to transition to next workflow status
 disable-model-invocation: true
 argument-hint: "<issue-number>"
 allowed-tools:
-  - mcp__workspace__github_issue_view
+  - mcp__mcp-workspace__github_issue_view
   - "Bash(gh issue comment *)"
   - "Bash(MSYS_NO_PATHCONV=1 gh issue comment *)"
-  - mcp__workspace__read_file
+  - mcp__mcp-workspace__read_file
 ---
 
 # Approve Issue
@@ -23,7 +23,7 @@ If no issue number is provided:
 
 ## Instructions
 
-1. Fetch the issue to confirm it exists using `mcp__workspace__github_issue_view`.
+1. Fetch the issue to confirm it exists using `mcp__mcp-workspace__github_issue_view`.
 
 2. Validate that the issue is ready for approval:
    - Issue has been analyzed/discussed

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/issue_create/SKILL.md

@@ -4,7 +4,7 @@ disable-model-invocation: true
 argument-hint: "<title>"
 allowed-tools:
   - "Bash(gh issue create *)"
-  - mcp__workspace__git
+  - mcp__mcp-workspace__git
 ---
 
 # Create GitHub Issue
@@ -31,7 +31,7 @@ Use cases:
 - Features building on existing work
 - Long-running feature branches
 
-**Important:** Before specifying a base branch, verify it exists using `mcp__workspace__git` with command `"ls_remote"` and args `["--heads", "origin", "<branch-name>"]`.
+**Important:** Before specifying a base branch, verify it exists using `mcp__mcp-workspace__git` with command `"ls_remote"` and args `["--heads", "origin", "<branch-name>"]`.
 
 If no base branch is needed, omit this section entirely.
 

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/issue_update/SKILL.md

@@ -4,12 +4,12 @@ disable-model-invocation: true
 argument-hint: "<issue-number>"
 allowed-tools:
   - "Bash(gh issue edit *)"
-  - mcp__workspace__github_issue_view
-  - mcp__workspace__save_file
-  - mcp__workspace__delete_this_file
-  - mcp__workspace__read_file
-  - mcp__workspace__list_directory
-  - mcp__workspace__search_files
+  - mcp__mcp-workspace__github_issue_view
+  - mcp__mcp-workspace__save_file
+  - mcp__mcp-workspace__delete_this_file
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__list_directory
+  - mcp__mcp-workspace__search_files
 ---
 
 # Update GitHub Issue
@@ -19,7 +19,7 @@ Based on our prior `/issue_analyse` discussion, update the GitHub issue with ref
 **Instructions:**
 1. If no issue context is found from prior analysis, respond: "No issue context found. Please run `/issue_analyse <number>` first."
 
-2. First, fetch the current issue content using `mcp__workspace__github_issue_view`.
+2. First, fetch the current issue content using `mcp__mcp-workspace__github_issue_view`.
 
 3. Draft updated issue text with:
    - Clear, concise title
@@ -27,7 +27,7 @@ Based on our prior `/issue_analyse` discussion, update the GitHub issue with ref
 
 4. Write the issue body to a temp file (avoids bash escaping issues with markdown):
 ```python
-mcp__workspace__save_file(file_path="issue_body_temp.md", content=body_content)
+mcp__mcp-workspace__save_file(file_path="issue_body_temp.md", content=body_content)
 ```
 
 5. Update the issue using `--body-file`:
@@ -37,7 +37,7 @@ gh issue edit <issue_number> --title "NEW_TITLE" --body-file issue_body_temp.md
 
 6. Clean up the temp file:
 ```python
-mcp__workspace__delete_this_file(file_path="issue_body_temp.md")
+mcp__mcp-workspace__delete_this_file(file_path="issue_body_temp.md")
 ```
 
 **Editing Base Branch:**

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/plan_review/SKILL.md

@@ -1,18 +1,17 @@
 ---
 description: Review implementation plan for completeness, simplicity, and risks
-disable-model-invocation: true
 allowed-tools:
-  - mcp__workspace__git
-  - mcp__workspace__read_file
-  - mcp__workspace__list_directory
-  - mcp__workspace__search_files
+  - mcp__mcp-workspace__git
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__list_directory
+  - mcp__mcp-workspace__search_files
 ---
 
 # Review Implementation Plan
 
 **First, ensure we're up to date:**
-Call `mcp__workspace__git` with command `"fetch"` and args `["origin"]`.
-Use `mcp__workspace__git` with command `"status"` to check working directory state.
+Call `mcp__mcp-workspace__git` with command `"fetch"` and args `["origin"]`.
+Use `mcp__mcp-workspace__git` with command `"status"` to check working directory state.
 
 Confirm and display the current feature branch name.
 

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/plan_review_supervisor/SKILL.md

@@ -2,14 +2,14 @@
 description: Autonomous plan review — supervisor delegates to engineer subagents
 disable-model-invocation: true
 allowed-tools:
-  - mcp__workspace__github_issue_view
-  - mcp__workspace__read_file
-  - mcp__workspace__save_file
-  - mcp__workspace__edit_file
-  - mcp__workspace__list_directory
-  - mcp__tools-py__run_pylint_check
-  - mcp__tools-py__run_pytest_check
-  - mcp__tools-py__run_mypy_check
+  - mcp__mcp-workspace__github_issue_view
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__save_file
+  - mcp__mcp-workspace__edit_file
+  - mcp__mcp-workspace__list_directory
+  - mcp__mcp-tools-py__run_pylint_check
+  - mcp__mcp-tools-py__run_pytest_check
+  - mcp__mcp-tools-py__run_mypy_check
 ---
 
 # Automated Plan Review / using a supervisor agent
@@ -18,7 +18,7 @@ You are a technical lead supervising a software engineer (subagent). You do not
 
 **Setup:**
 
-1. Read the GitHub issue (using `mcp__workspace__github_issue_view`), `pr_info/steps/summary.md`, and `pr_info/steps/Decisions.md` (if it exists) to understand requirements and design decisions.
+1. Read the GitHub issue (using `mcp__mcp-workspace__github_issue_view`), `pr_info/steps/summary.md`, and `pr_info/steps/Decisions.md` (if it exists) to understand requirements and design decisions.
 2. Read the knowledge base files:
    - `.claude/knowledge_base/software_engineering_principles.md`
    - `.claude/knowledge_base/planning_principles.md`
@@ -65,6 +65,6 @@ You are a technical lead supervising a software engineer (subagent). You do not
 **Status**: {committed / no changes needed}
 ```
 
-**Subagent instructions:** Remind subagents to follow CLAUDE.md (MCP tools, no `cd` prefix, approved commands only).
+**Subagent instructions:** When launching subagents, instruct them to follow CLAUDE.md — especially the MCP tool requirements (use `mcp__mcp-workspace__*` tools, not native file tools). Also remind them: no `cd` prefix, approved commands only.
 
 **Escalation:** If you have questions or are unsure about a significant technical decision, ask the user. For borderline improvements, default to simpler plans rather than asking — only escalate when the change affects scope or architecture.

{mcp_coder_utils-0.1.4 → mcp_coder_utils-0.1.6}/.claude/skills/plan_update/SKILL.md

@@ -1,11 +1,10 @@
 ---
 description: Update implementation plan files based on discussion
-disable-model-invocation: true
 allowed-tools:
-  - mcp__workspace__read_file
-  - mcp__workspace__save_file
-  - mcp__workspace__edit_file
-  - mcp__workspace__list_directory
+  - mcp__mcp-workspace__read_file
+  - mcp__mcp-workspace__save_file
+  - mcp__mcp-workspace__edit_file
+  - mcp__mcp-workspace__list_directory
 ---
 
 # Update Plan Files