onetool-mcp 1.0.0rc2__tar.gz → 1.0.0rc3__tar.gz

{onetool_mcp-1.0.0rc2 → onetool_mcp-1.0.0rc3}/.claude/commands/proj/consult.md

@@ -1,63 +1,104 @@
----
-name: Consult
-description: Interactive consultation mode for research and Q&A. Can save findings on explicit request.
-category: onetool
-tags: [consultation, research, qa, findings]
----
-
-**Assumptions**
-- Uses openspec (`openspec/project.md` for context)
-- Language agnostic
-
-**Guardrails**
-- This is primarily a READ-ONLY consultation session. You MUST NOT:
-  - Make git commits or push changes
-  - Run commands that modify the system (e.g., `git commit`, `rm`, `mv`, `npm install`)
-  - Modify existing project source code
-- You CAN and SHOULD:
-  - Read files, search code, and explore the codebase
-  - Run read-only commands (e.g., `git log`, `git status`, `git diff`, `ls`, `cat`)
-  - Use web search for up-to-date information
-  - Answer questions thoroughly with code references
-  - Ask clarifying questions to understand user needs
-- **Writing Findings (on explicit request only)**:
-  - When the user explicitly asks to save, write, or document findings (e.g., "save these findings", "write this up", "document what we found"):
-    - Suggest a descriptive filename based on the topic discussed
-    - Write findings to `plan/consult/<name>.md` (create directory if needed)
-    - Unless user specifies a different location
-    - Use a clear heading with date/time and topic
-    - Include key discoveries, code references, and conclusions
-  - Do NOT write findings unless the user explicitly requests it
-- The session continues until the user explicitly ends it (e.g., "end consultation", "done consulting", "exit consult mode").
-
-**Steps**
-1. Begin the consultation:
-   - Acknowledge entering consultation mode.
-   - Briefly explain the read-only constraints.
-   - Ask what the user would like to explore or discuss.
-2. Handle each question:
-   - Listen to the user's question or topic.
-   - Use read-only tools (Read, Glob, Grep, WebSearch, WebFetch, Task with Explore agent) to research.
-   - Provide clear, detailed answers with file references where relevant.
-   - Ask follow-up questions if clarification is needed.
-3. Continue the dialogue:
-   - After answering, check if the user has more questions.
-   - Offer to dive deeper into related topics.
-   - Suggest areas that might be worth exploring.
-4. Save findings (on explicit request):
-   - When user asks to save/document findings:
-     - Suggest a filename: "I'll save this as `plan/consult/<topic>.md` - sound good?"
-     - Create `plan/consult/` directory if it doesn't exist
-     - Write with dated heading and key discoveries
-     - Confirm what was written
-5. End the session:
-   - When the user signals they are done (e.g., "end consultation", "done", "exit"):
-     - Summarize key findings from the session.
-     - Suggest next steps if applicable (e.g., creating a proposal, making changes).
-     - Confirm the session has ended.
-
-**Reference**
-- Use exploration agents (Task with subagent_type=Explore) for open-ended codebase questions.
-- Reference files using markdown link format: `[filename.ts](path/to/file.ts)`.
-- For web research, cite sources in your answers.
-- Cross-reference with `openspec/project.md` for project context when relevant.
+---
+name: Consult
+description: Interactive consultation mode for research and Q&A. Can save findings on explicit request.
+category: onetool
+tags: [consultation, research, qa, findings]
+---
+
+**Assumptions**
+- Uses openspec (`openspec/project.md` for context)
+- Language agnostic
+
+**Output Structure**
+Findings are organized into two parts:
+
+**Part 1: Recommendations**
+- Detailed changes that will be implemented
+- Starts EMPTY at the beginning of consultation
+- Only filled in once the way forward is clear
+- Written in enough detail to be used in an openspec proposal
+- Should include specific file paths, function signatures, and implementation details
+
+**Part 2: Analysis and Options**
+- Research findings, discoveries, and explorations
+- Filled during the consultation as you explore the codebase
+- Include code references, patterns found, and architectural insights
+- Present multiple options or approaches when applicable
+- Note trade-offs, risks, and considerations
+
+**Guardrails**
+- This is primarily a READ-ONLY consultation session. You MUST NOT:
+  - Make git commits or push changes
+  - Run commands that modify the system (e.g., `git commit`, `rm`, `mv`, `npm install`)
+  - Modify existing project source code
+- You CAN and SHOULD:
+  - Read files, search code, and explore the codebase
+  - Run read-only commands (e.g., `git log`, `git status`, `git diff`, `ls`, `cat`)
+  - Use web search for up-to-date information
+  - Answer questions thoroughly with code references
+  - Ask clarifying questions to understand user needs
+- **Writing Findings (on explicit request only)**:
+  - When the user explicitly asks to save, write, or document findings (e.g., "save these findings", "write this up", "document what we found"):
+    - Suggest a descriptive filename based on the topic discussed
+    - Write findings to `wip/consult/<name>.md`
+    - Unless user specifies a different location
+    - Use the two-part structure (Recommendations + Analysis)
+    - Include dated heading and topic
+  - Do NOT write findings unless the user explicitly requests it
+- The session continues until the user explicitly ends it (e.g., "end consultation", "done consulting", "exit consult mode").
+
+**Steps**
+1. Begin the consultation:
+   - Acknowledge entering consultation mode.
+   - Briefly explain the read-only constraints and two-part structure.
+   - Ask what the user would like to explore or discuss.
+
+2. Research and explore (Part 2: Analysis and Options):
+   - Listen to the user's question or topic.
+   - Use read-only tools (Read, Glob, Grep, WebSearch, WebFetch, Task with Explore agent) to research.
+   - Build up findings in Part 2: Analysis and Options:
+     - Document discoveries, patterns, and code references
+     - Present multiple approaches when applicable
+     - Note trade-offs and considerations
+   - Provide clear, detailed answers with file references where relevant.
+   - Ask follow-up questions if clarification is needed.
+
+3. Continue the dialogue:
+   - After answering, check if the user has more questions.
+   - Offer to dive deeper into related topics.
+   - Suggest areas that might be worth exploring.
+   - When the way forward becomes clear, offer to move to recommendations.
+
+4. Formulate recommendations (Part 1: Recommendations):
+   - Once the approach is decided:
+     - Write detailed, actionable recommendations in Part 1
+     - Include specific file paths, function signatures, implementation details
+     - Make recommendations detailed enough to be used in an openspec proposal
+     - Keep Part 2 as supporting analysis
+
+5. Save findings (on explicit request):
+   - When user asks to save/document findings:
+     - Suggest a filename: "I'll save this as `wip/consult/<topic>.md` - sound good?"
+     - Write using the two-part structure:
+       ```markdown
+       # [Topic] - [Date]
+
+       ## Part 1: Recommendations
+       [Detailed changes to implement - may be empty initially]
+
+       ## Part 2: Analysis and Options
+       [Research findings, discoveries, code references]
+       ```
+     - Confirm what was written
+
+6. End the session:
+   - When the user signals they are done (e.g., "end consultation", "done", "exit"):
+     - Summarize key findings from the session.
+     - Suggest next steps if applicable (e.g., creating a proposal, making changes).
+     - Confirm the session has ended.
+
+**Reference**
+- Use exploration agents (Task with subagent_type=Explore) for open-ended codebase questions.
+- Reference files using markdown link format: `[filename.ts](path/to/file.ts)`.
+- For web research, cite sources in your answers.
+- Cross-reference with `openspec/project.md` for project context when relevant.

{onetool_mcp-1.0.0rc2 → onetool_mcp-1.0.0rc3}/.claude/commands/proj/sanity.md

@@ -12,11 +12,11 @@ Parse the user's input for these optional arguments:
 - `retest=all` - Run full test suite
 - `retest=failed` - Retest only areas with status "partial" or "fail"
 
-If no argument provided, check `tests/sanity/test_sanity_status.yaml` and suggest retesting failed/partial areas.
+If no argument provided, check `wip/test-results/sanity-report.yaml` and suggest retesting failed/partial areas.
 
 ## Setup
 
-1. Read `tests/sanity/test_sanity_status.yaml` to see current test status
+1. Read `wip/test-results/sanity-report.yaml` to see current test status
 2. Read `tests/sanity/test_sanity-hints.md` for efficiency tips
 3. Read `tests/sanity/test_sanity.md` for test definitions
 4. For all prompts, explain what you are doing with 💭
@@ -34,11 +34,11 @@ Based on the `retest` argument:
 
 When errors are encountered, check if they are caused by:
 - **Your mistake**: Add a hint to `tests/sanity/test_sanity-hints.md` to avoid in future
-- **OneTool defect**: Create `./plan/issues/{issue-name}.md` with issue details
+- **OneTool defect**: Create `wip/issues/{issue-name}.md` with issue details
 
 ## Status Update
 
-After testing each area, update `tests/sanity/test_sanity_status.yaml`:
+After testing each area, update `wip/test-results/sanity-report.yaml`:
 - Set `status` to: `pass`, `partial`, or `fail`
 - Set `date` to today's date (YYYY-MM-DD)
 - Update `checks` list with tools tested
@@ -61,5 +61,6 @@ brave:
 - Mark hints added as 🔹
 - Keep a list of issues and hints, grouped by component
 - Show summary table at end with pass/partial/fail counts
+- All test tracking and results are stored in `wip/test-results/sanity-report.yaml`
 
-**DO NOT MAKE CODE CHANGES** - only create issue files, hint entries, and status updates.
+**DO NOT MAKE CODE CHANGES** - only create issue files, hint entries, status updates, and test result reports.

onetool_mcp-1.0.0rc3/.claude/commands/proj/stage.md

@@ -0,0 +1,158 @@
+# Stage Changes for Commit
+
+Stage files for a logical change and suggest a conventional commit message.
+
+## Behavior
+
+1. **Analyze Changed Files**
+   - Run `git status --short` to see all changes
+   - Run `git diff --cached` for staged changes (if any)
+   - Run `git diff` for unstaged changes
+   - Identify the primary change type and scope
+
+2. **Stage Related Files**
+   - Ask user which files to stage (if not already specified)
+   - Stage files with `git add <files>`
+   - Confirm staging with `git status --short`
+
+3. **Suggest Commit Message**
+   - Analyze the staged changes
+   - Use type/scope of the MOST IMPORTANT change
+   - List all changes in description (most important first)
+   - Generate a conventional commit message:
+     ```
+     <type>(scope): <description>
+     Ref: #123
+     ```
+   - Description: 50-72 chars ideal, can be longer if needed
+   - Multiple changes: separate with commas
+   - Second line for issue reference only (if applicable)
+
+## Commit Message Format
+
+### Type (required)
+- `feat` - New feature or capability
+- `fix` - Bug fix
+- `refactor` - Code restructuring without behavior change
+- `perf` - Performance improvement
+- `docs` - Documentation changes
+- `test` - Test additions or changes
+- `build` - Build system or dependency changes
+- `ci` - CI/CD pipeline changes
+- `chore` - Maintenance tasks (cleanup, formatting, etc.)
+- `style` - Code style/formatting (no logic change)
+- `revert` - Revert a previous commit
+
+### Scope (optional but recommended)
+
+**Core Systems:**
+- `config` - Configuration system (loader, models, secrets)
+- `cli` - Command-line interface (onetool, bench CLIs)
+- `serve` - MCP server functionality
+- `proxy` - MCP proxy/client functionality
+- `security` - Security validation and policies
+- `stats` - Statistics collection and reporting
+- `logging` - Logging infrastructure
+
+**Tool Packs** (use format `tool:name`):
+- `tool:brave` - Brave search
+- `tool:code` - Code search
+- `tool:context7` - Context7 documentation
+- `tool:convert` - Document conversion
+- `tool:db` - Database operations
+- `tool:diagram` - Diagram generation
+- `tool:excel` - Excel operations
+- `tool:file` - File operations
+- `tool:ground` - Grounding search
+- `tool:llm` - LLM transform
+- `tool:ot` - Meta/introspection tools
+- `tool:package` - Package info
+- `tool:ripgrep` - Code search
+- `tool:scaffold` - Tool scaffolding
+- `tool:web` - Web fetch
+
+**Benchmark:**
+- `bench` - Benchmark harness
+- `bench:config` - Benchmark configuration
+- `bench:harness` - Benchmark execution
+- `bench:metrics` - Metrics collection
+- `bench:tui` - Terminal UI
+
+**Other:**
+- `deps` - Dependency updates
+- `release` - Release preparation
+- `demo` - Demo/example code
+- `dx` - Developer experience
+
+### Description (required)
+- Use imperative mood: "add feature" not "added feature"
+- Start with lowercase
+- No period at the end
+- Keep concise: 50-72 chars ideal, longer OK if needed
+- Be specific and descriptive
+
+### Issue Reference (optional)
+- Add `Ref: #123` on second line if there's an issue
+- Use singular "Ref" not "Refs"
+
+## Examples
+
+### Single Change ✅
+```
+feat(tool:brave): add news search endpoint
+fix(config): resolve include paths from ot_dir not config_dir
+refactor(config): remove project-level configuration support
+perf(tool:ripgrep): reduce token usage by 50%
+```
+
+### Multiple Changes (most important first) ✅
+```
+feat(config): add compact array format, update security template, fix tests
+fix(tool:brave): prevent racing, add retry logic, improve error handling
+refactor(config): simplify loader, remove inheritance, flatten includes
+docs: update readme, fix typos in contributing guide, add examples
+```
+
+### With Issue Reference ✅
+```
+fix(tool:brave): prevent racing of requests, add retry logic
+Ref: #123
+```
+
+### Bad Examples ❌
+```
+❌ Added news search and fixed a bug
+   (past tense, no scope/type)
+
+❌ feat(tool:brave): Add news search endpoint.
+   (capitalized, has period)
+
+❌ fix: bug fixes
+   (too vague)
+
+❌ Refs: #123
+   (use "Ref" not "Refs")
+```
+
+## Usage
+
+Simply call `/proj:stage` and the agent will:
+1. Show you the current git status
+2. Analyze the changes
+3. Ask which files you want to stage (or stage all related files)
+4. Stage the files
+5. Suggest a conventional commit message based on the changes
+
+The agent will NOT commit - it only stages and suggests. You can then:
+- Accept the suggested message and commit manually
+- Modify the message and commit
+- Use `/commit` slash command with the suggested message
+- Continue making changes before committing
+
+## Notes
+
+- **DO NOT commit** - this command only stages
+- Focus on logical, atomic changes
+- One change type per commit (don't mix feat + fix)
+- If changes span multiple areas, consider multiple commits
+- Breaking changes should include migration notes in body

{onetool_mcp-1.0.0rc2 → onetool_mcp-1.0.0rc3}/.claude/settings.local.json

@@ -138,7 +138,11 @@
       "Bash(zsh -c 'read \"\"confirm?Test: \"\" && echo \"\"got: [$confirm]\"\"')",
       "Bash(zsh -c 'read \"\"confirm?Test: \"\" && [ \"\"$confirm\"\" = \"\"y\"\" ] && echo \"\"matched\"\"')",
       "WebFetch(domain:static.modelcontextprotocol.io)",
-      "Bash(mcp-publisher:*)"
+      "Bash(mcp-publisher:*)",
+      "Bash(test:*)",
+      "mcp__onetool-dev__run",
+      "Bash(UV_HTTP_TIMEOUT=120 uv sync:*)",
+      "Bash(.venv/bin/onetool:*)"
     ]
   },
   "enableAllProjectMcpServers": true,

{onetool_mcp-1.0.0rc2 → onetool_mcp-1.0.0rc3}/.github/workflows/publish.yml

@@ -1,63 +1,64 @@
-name: Publish
-#
-# Manual trigger → TestPyPI
-# Release trigger → PyPI
-
-on:
-  workflow_dispatch:  # Manual trigger for TestPyPI
-  release:
-    types: [published]  # Automatic trigger for PyPI
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v6.0.1
-
-      - name: Install uv
-        uses: astral-sh/setup-uv@v7.2.0
-
-      - name: Build package
-        run: uv build
-
-      - name: Upload artifacts
-        uses: actions/upload-artifact@v6.0.0
-        with:
-          name: dist
-          path: dist/
-
-  publish-testpypi:
-    if: github.event_name == 'workflow_dispatch'
-    needs: build
-    runs-on: ubuntu-latest
-    environment: testpypi
-    permissions:
-      id-token: write
-    steps:
-      - name: Download artifacts
-        uses: actions/download-artifact@v7.0.0
-        with:
-          name: dist
-          path: dist/
-
-      - name: Publish to TestPyPI
-        uses: pypa/gh-action-pypi-publish@v1.13.0
-        with:
-          repository-url: https://test.pypi.org/legacy/
-
-  publish-pypi:
-    if: github.event_name == 'release'
-    needs: build
-    runs-on: ubuntu-latest
-    environment: pypi
-    permissions:
-      id-token: write
-    steps:
-      - name: Download artifacts
-        uses: actions/download-artifact@v7.0.0
-        with:
-          name: dist
-          path: dist/
-
-      - name: Publish to PyPI
-        uses: pypa/gh-action-pypi-publish@v1.13.0
+name: Publish
+#
+# Manual trigger → TestPyPI
+# Release trigger → PyPI
+
+on:
+  workflow_dispatch:  # Manual trigger for TestPyPI
+  release:
+    types: [published]  # Automatic trigger for PyPI
+
+jobs:
+  build:
+    if: false  # Temporarily disabled - using manual release workflow
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6.0.1
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v7.2.0
+
+      - name: Build package
+        run: uv build
+
+      - name: Upload artifacts
+        uses: actions/upload-artifact@v6.0.0
+        with:
+          name: dist
+          path: dist/
+
+  publish-testpypi:
+    if: github.event_name == 'workflow_dispatch'
+    needs: build
+    runs-on: ubuntu-latest
+    environment: testpypi
+    permissions:
+      id-token: write
+    steps:
+      - name: Download artifacts
+        uses: actions/download-artifact@v7.0.0
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to TestPyPI
+        uses: pypa/gh-action-pypi-publish@v1.13.0
+        with:
+          repository-url: https://test.pypi.org/legacy/
+
+  publish-pypi:
+    if: github.event_name == 'release'
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - name: Download artifacts
+        uses: actions/download-artifact@v7.0.0
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@v1.13.0