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

{onetool_mcp-1.0.0b1 → onetool_mcp-1.0.0rc2}/.chunkhound.json

@@ -1,37 +1,37 @@
-{
-  "database": {
-    "provider": "duckdb"
-  },
-  "embedding": {
-    "provider": "openai",
-    "model": "text-embedding-3-small",
-    "base_url": "https://openrouter.ai/api/v1"
-  },
-  "indexing": {
-    "include": [
-      "**/*.py",
-      "**/*.md",
-      "**/*.yaml",
-      "**/*.toml",
-      "**/*.json"
-    ],
-    "exclude": [
-      "**/node_modules/**",
-      "**/__pycache__/**",
-      "**/.venv/**",
-      "**/dist/**",
-      "**/build/**",
-      "**/*.egg-info/**",
-      "**/.git/**",
-      "**/.local/**",
-      "**/htmlcov/**",
-      "**/.mypy_cache/**",
-      "**/.pytest_cache/**",
-      "**/.ruff_cache/**"
-    ]
-  },
-  "mcp": {
-    "transport": "stdio"
-  },
-  "debug": false
-}
+{
+  "database": {
+    "provider": "duckdb"
+  },
+  "embedding": {
+    "provider": "openai",
+    "model": "text-embedding-3-small",
+    "base_url": "https://openrouter.ai/api/v1"
+  },
+  "indexing": {
+    "include": [
+      "**/*.py",
+      "**/*.md",
+      "**/*.yaml",
+      "**/*.toml",
+      "**/*.json"
+    ],
+    "exclude": [
+      "**/node_modules/**",
+      "**/__pycache__/**",
+      "**/.venv/**",
+      "**/dist/**",
+      "**/build/**",
+      "**/*.egg-info/**",
+      "**/.git/**",
+      "**/.local/**",
+      "**/htmlcov/**",
+      "**/.mypy_cache/**",
+      "**/.pytest_cache/**",
+      "**/.ruff_cache/**"
+    ]
+  },
+  "mcp": {
+    "transport": "stdio"
+  },
+  "debug": false
+}

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

@@ -1,63 +1,63 @@
----
-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
+
+**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.

{onetool_mcp-1.0.0b1 → onetool_mcp-1.0.0rc2}/.claude/commands/proj/prime.md

@@ -1,8 +1,8 @@
----
-name: Prime
-description: Load project context from AGENTS_PRIME.md
----
-
-Read and present the contents of `AGENTS_PRIME.md` to prime the conversation with project context.
-
-After reading, briefly confirm the context is loaded and ask what the user would like to work on.
+---
+name: Prime
+description: Load project context from agents/prime.md
+---
+
+Read and present the contents of `agents/prime.md` to prime the conversation with project context.
+
+After reading, briefly confirm the context is loaded and ask what the user would like to work on.

{onetool_mcp-1.0.0b1 → onetool_mcp-1.0.0rc2}/.claude/commands/proj/quick-apply.md

@@ -52,10 +52,19 @@ If input is unclear, ASK the user to clarify before proceeding.
 3. Identify all affected areas:
    - Source files to modify
    - Tests to add/update
-   - Specs to update
+   - Specs to update (search `openspec/specs/` for related specs - see detection rules below)
    - Docs to sync
    - Config to migrate
 
+### Spec Detection Rules
+
+To find affected specs, check for specs matching these patterns:
+- **Tool changes** (`src/ot_tools/<name>.py`): Look for `openspec/specs/tool-<name>/spec.md`
+- **Serve/server changes** (`src/ot/`): Look for `openspec/specs/serve-*/spec.md`
+- **Feature/pack changes**: Search spec files for the feature name: `rg "<feature>" openspec/specs/`
+
+If a spec exists for the functionality being modified, it MUST be updated.
+
 ---
 
 ## Step 2: Present the Plan
@@ -110,14 +119,22 @@ Report test results before proceeding.
 
 ## Step 5: Update Specs
 
-If specs exist for the changed functionality:
+**ALWAYS check for affected specs before skipping this step.**
+
+1. **Find related specs** using these strategies:
+   - For tool changes (`src/ot_tools/<name>.py`): Check `openspec/specs/tool-<name>/spec.md`
+   - For serve changes: Check `openspec/specs/serve-*/spec.md`
+   - Search for the feature name: `ls openspec/specs/ | grep <feature>`
+   - Search spec contents: `rg "<function_name>" openspec/specs/`
+
+2. **If a spec exists**, update it to match the new implementation:
+   - Add new requirements/scenarios for new functionality
+   - Update existing scenarios if behavior changed
+   - Ensure all function signatures and parameters are documented
 
-1. Locate relevant specs in `openspec/specs/`
-2. Update requirements to match new implementation
-3. Update or add scenarios as needed
-4. Run `openspec validate --strict` if available
+3. Run `openspec validate --strict` if available
 
-Skip this step if no specs are affected.
+Only skip this step if you have explicitly verified NO specs exist for the changed functionality.
 
 ---