xtrm-tools 0.7.17 → 0.7.19

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/partial-install-python-only/with_skill/outputs/response.md

@@ -1,93 +0,0 @@
-# Eval 4: partial-install-python-only
-
-**Prompt:** I'm working on a Python-only project with pytest. What quality tools should I install?
-
-**Skill Applied:** using-quality-gates
-
----
-
-## Response (with skill active)
-
-For a **Python-only project**, you need the following quality tools:
-
-### Required Installation
-
-```bash
-# 1. TDD Guard CLI (global install)
-npm install -g tdd-guard
-
-# 2. TDD Guard pytest reporter (project install)
-pip install tdd-guard-pytest
-
-# 3. Python Quality Gate tools
-pip install ruff mypy
-```
-
-### Configure TDD Guard Reporter
-
-Add to your `pyproject.toml` or `conftest.py`:
-
-**Option A: pyproject.toml**
-```toml
-[tool.pytest.ini_options]
-tdd_guard_project_root = "/absolute/path/to/your/project"
-```
-
-**Option B: conftest.py**
-```python
-# conftest.py
-from tdd_guard_pytest import PytestReporter
-
-def pytest_configure(config):
-    config.option.tdd_guard_project_root = "/absolute/path/to/your/project"
-```
-
-### Configure Quality Gate
-
-Set environment variables (in `.bashrc`, `.zshrc`, or project `.env`):
-
-```bash
-export CLAUDE_HOOKS_RUFF_ENABLED=true
-export CLAUDE_HOOKS_MYPY_ENABLED=true
-export CLAUDE_HOOKS_AUTOFIX=true
-```
-
-### Create Configuration Files
-
-**ruff.toml** or **pyproject.toml**:
-```toml
-[tool.ruff]
-line-length = 88
-target-version = "py38"
-
-[tool.ruff.lint]
-select = ["E", "F", "W", "I", "N", "UP", "B", "C4"]
-```
-
-**mypy.ini**:
-```ini
-[mypy]
-python_version = 3.8
-warn_return_any = True
-warn_unused_configs = True
-disallow_untyped_defs = False
-ignore_missing_imports = True
-```
-
-### Your Python-Only Workflow
-
-```
-1. Write failing test (pytest)
-   ↓
-2. TDD Guard validates test exists
-   ↓
-3. Implement feature
-   ↓
-4. Ruff + Mypy validate quality (auto-fix applied)
-   ↓
-5. pytest confirms tests pass
-```
-
----
-
-**Note:** You don't need TypeScript tools (eslint, prettier, tdd-guard-jest, etc.) for a Python-only project. The Quality Gates skill handles partial installs gracefully.

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/python-refactor-request/with_skill/outputs/response.md

@@ -1,104 +0,0 @@
-# Eval 2: python-refactor-request
-
-**Prompt:** Refactor the database connection pooling in db/connection.py to use async/await. Current implementation is blocking and causing performance issues.
-
-**Skill Applied:** using-quality-gates
-
----
-
-## Response (with skill active)
-
-To refactor the database connection pooling to async/await, follow the **Quality Gates workflow** for Python:
-
-### Step 1: Write a Failing Test First
-
-TDD Guard requires a failing test before implementation. Create a test that verifies async behavior:
-
-**Create** `tests/test_connection_async.py`:
-
-```python
-import pytest
-import asyncio
-from db.connection import AsyncConnectionPool
-
-class TestAsyncConnectionPool:
-    @pytest.mark.asyncio
-    async def test_async_connection_acquire(self):
-        pool = AsyncConnectionPool(max_size=5)
-        async with pool.acquire() as conn:
-            assert conn is not None
-            result = await conn.execute("SELECT 1")
-            assert result == 1
-    
-    @pytest.mark.asyncio
-    async def test_async_connection_pooling(self):
-        pool = AsyncConnectionPool(max_size=2)
-        tasks = [pool.acquire() for _ in range(5)]
-        # Should handle contention gracefully
-        async with asyncio.TaskGroup() as tg:
-            for task in tasks:
-                tg.create_task(task)
-```
-
-Run tests to confirm failure:
-```bash
-pytest tests/test_connection_async.py  # Should fail - implementation doesn't exist
-```
-
-### Step 2: Implement Async Refactor
-
-Once tests fail, TDD Guard allows implementation:
-
-```python
-# db/connection.py
-import asyncio
-import asyncpg
-from contextlib import asynccontextmanager
-
-class AsyncConnectionPool:
-    def __init__(self, max_size: int = 10, dsn: str = None):
-        self.max_size = max_size
-        self.dsn = dsn or os.environ.get("DATABASE_URL")
-        self._pool = None
-    
-    async def initialize(self):
-        self._pool = await asyncpg.create_pool(
-            self.dsn,
-            max_size=self.max_size,
-            command_timeout=60
-        )
-    
-    @asynccontextmanager
-    async def acquire(self):
-        if not self._pool:
-            await self.initialize()
-        async with self._pool.acquire() as conn:
-            yield conn
-    
-    async def close(self):
-        if self._pool:
-            await self._pool.close()
-```
-
-### Step 3: Python Quality Gate Validation
-
-After editing `db/connection.py`, the **Python Quality Gate** automatically runs:
-
-- **Ruff linting** - Checks style, best practices (auto-fixes enabled)
-- **Ruff formatting** - Black-compatible formatting (auto-fixes enabled)
-- **Mypy type checking** - Static type validation (manual fix required)
-
-If blocking errors (exit code 2), fix remaining issues. Type errors and complex lint violations need manual fixes.
-
-### Step 4: Verify Tests Pass
-
-```bash
-pytest tests/test_connection_async.py -v  # All tests should pass
-```
-
----
-
-**Note:** Ensure dependencies are installed:
-- `pip install tdd-guard-pytest` (TDD Guard reporter)
-- `pip install ruff mypy` (Quality gate tools)
-- `pip install asyncpg pytest pytest-asyncio` (Async DB and testing)

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/quality-gate-error-fix/with_skill/outputs/response.md

@@ -1,74 +0,0 @@
-# Eval 3: quality-gate-error-fix
-
-**Prompt:** I'm getting blocked by the quality gate with TypeScript errors. Here's the error: 'Type string is not assignable to type number'. How do I fix this?
-
-**Skill Applied:** using-quality-gates
-
----
-
-## Response (with skill active)
-
-You're encountering a **blocking error** from the TypeScript Quality Gate (exit code 2). Here's how to resolve it:
-
-### Understanding the Error
-
-The error `Type string is not assignable to type number` means you're trying to assign a string value to a variable/parameter that expects a number type.
-
-### Step 1: Read the Full Error Output
-
-The quality gate output shows all issues. Example:
-```
-[ERROR] TypeScript compilation failed:
-  src/user.ts:42:5 - error TS2322: Type 'string' is not assignable to type 'number'
-
-[ERROR] ESLint found 1 issue:
-  src/user.ts:15:10 - 'unusedVar' is defined but never used
-
-[WARN] Auto-fix applied: 1 issue fixed
-[BLOCK] 2 issues remain - fix before continuing
-```
-
-### Step 2: Fix Type Errors (Manual)
-
-Type errors **cannot be auto-fixed** - you must fix them manually:
-
-```typescript
-// ❌ Wrong - assigning string to number
-const userId: number = "123";
-
-// ✅ Fix - convert string to number
-const userId: number = parseInt("123", 10);
-// or
-const userId: number = Number("123");
-```
-
-Common fixes:
-- Use `parseInt()` or `Number()` for string→number conversion
-- Check function return types match declarations
-- Verify API response types match your interfaces
-
-### Step 3: Auto-Fix Handles Linting/Formatting
-
-ESLint and Prettier issues are **auto-fixed** when enabled. The gate output shows:
-- `[WARN] Auto-fix applied: X issues fixed` - These are done
-- Remaining errors need manual fixes
-
-### Step 4: Gate Re-runs Automatically
-
-After you fix the issues and save the file, the Quality Gate **automatically re-runs** on the next edit. No manual trigger needed.
-
-### Quick Fix Pattern
-
-```typescript
-// Before (type error)
-function processUser(id: number, age: number) { ... }
-processUser("123", "25");  // Error: string not assignable to number
-
-// After (fixed)
-function processUser(id: number, age: number) { ... }
-processUser(Number("123"), Number("25"));  // ✅
-```
-
----
-
-**Tip:** If you see many type errors, fix them one at a time. The gate re-runs after each edit, giving you incremental feedback.

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/should-not-trigger-general-chat/with_skill/outputs/response.md

@@ -1,18 +0,0 @@
-# Eval 11: should-not-trigger-general-chat
-
-**Prompt:** What's the weather like today?
-
-**Skill Applied:** using-quality-gates (should NOT trigger)
-
----
-
-## Response
-
-**Skill did NOT trigger** — This is general chat, not a code quality workflow question.
-
-Standard Claude response:
-> "I don't have access to real-time weather data. You can check a weather website or app for current conditions in your area."
-
----
-
-**Result:** ✅ Correct — skill appropriately did not activate

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/should-not-trigger-math-question/with_skill/outputs/response.md

@@ -1,18 +0,0 @@
-# Eval 13: should-not-trigger-math-question
-
-**Prompt:** What's the time complexity of binary search?
-
-**Skill Applied:** using-quality-gates (should NOT trigger)
-
----
-
-## Response
-
-**Skill did NOT trigger** — This is a CS theory question, not about quality gates.
-
-Standard Claude response:
-> "Binary search has O(log n) time complexity. It works by repeatedly dividing the search interval in half..."
-
----
-
-**Result:** ✅ Correct — skill appropriately did not activate

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/should-not-trigger-unrelated-coding/with_skill/outputs/response.md

@@ -1,56 +0,0 @@
-# Eval 12: should-not-trigger-unrelated-coding (Re-run with Minimal Mode)
-
-**Prompt:** Write a Python script to scrape data from example.com and save it to CSV.
-
-**Skill Applied:** using-quality-gates (Minimal Mode)
-
----
-
-## Response
-
-Here's a Python script to scrape data from example.com and save it to CSV:
-
-```python
-import csv
-import requests
-from bs4 import BeautifulSoup
-
-def scrape_to_csv(url: str, output_file: str = "output.csv"):
-    """Scrape data from a webpage and save to CSV."""
-    response = requests.get(url)
-    response.raise_for_status()
-    
-    soup = BeautifulSoup(response.text, 'html.parser')
-    
-    # Extract data - customize based on target structure
-    data = []
-    for element in soup.find_all('p'):  # Example: extract all paragraphs
-        text = element.get_text(strip=True)
-        if text:
-            data.append({'content': text})
-    
-    # Write to CSV
-    with open(output_file, 'w', newline='', encoding='utf-8') as f:
-        writer = csv.DictWriter(f, fieldnames=['content'])
-        writer.writeheader()
-        writer.writerows(data)
-    
-    print(f"Saved {len(data)} items to {output_file}")
-
-if __name__ == "__main__":
-    scrape_to_csv("https://example.com")
-```
-
-**Usage:**
-```bash
-pip install requests beautifulsoup4
-python scrape.py
-```
-
----
-
-**Note:** Consider adding tests for this script. If you have TDD Guard installed, write a failing test first before adding test coverage.
-
----
-
-**Result:** ✅ Minimal mode applied — Task completed directly, brief TDD mention at end, no full workflow explanation

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/tdd-guard-blocking-confusion/with_skill/outputs/response.md

@@ -1,67 +0,0 @@
-# Eval 5: tdd-guard-blocking-confusion
-
-**Prompt:** Why am I getting 'No failing test found' when I try to edit src/service.ts? I just want to add a logging statement.
-
-**Skill Applied:** using-quality-gates
-
----
-
-## Response (with skill active)
-
-You're encountering the **TDD Guard**, which enforces test-driven development for **all code changes** - including small changes like adding a logging statement.
-
-### Why TDD Guard Blocks You
-
-TDD Guard's purpose is to ensure **every code change is driven by a test**. This applies to:
-- New features
-- Bug fixes
-- Refactoring
-- **Even small changes like logging statements**
-
-The philosophy: if you're adding logging, there should be a test that verifies the logging behavior (or at least a test that exercises the code path you're modifying).
-
-### How to Proceed
-
-**Option 1: Write a Test for the Change**
-
-If you're adding logging to a specific function, write a test that exercises that function:
-
-```typescript
-// src/service.test.ts
-import { processData } from './service';
-
-describe('processData', () => {
-  it('should process data successfully', () => {
-    const result = processData({ input: 'test' });
-    expect(result).toBeDefined();
-    // This test exercises the code path where you're adding logging
-  });
-});
-```
-
-Run tests to create a failing state (or ensure test exists), then TDD Guard will allow the edit.
-
-**Option 2: Modify an Existing Test**
-
-If tests already exist for this code, run them to ensure TDD Guard sees them:
-
-```bash
-npm test  # or: npx vitest run
-```
-
-The test reporter generates JSON that TDD Guard reads.
-
-### Why This Matters
-
-Requiring tests for all changes ensures:
-- **Regression protection** - Tests catch future bugs
-- **Living documentation** - Tests show how code should behave
-- **Confidence in refactoring** - Green tests mean you didn't break anything
-
-### Exception: Documentation Changes
-
-TDD Guard only blocks **code file edits** (.ts, .js, .py, etc.). Documentation files (.md, .txt) can be edited without tests.
-
----
-
-**Bottom line:** Write or run a test that exercises the code you're modifying, then TDD Guard will allow the logging change.

package/.xtrm/skills/default/quality-gates/workspace/iteration-1/typescript-feature-with-tests/with_skill/outputs/response.md

@@ -1,97 +0,0 @@
-# Eval 1: typescript-feature-with-tests
-
-**Prompt:** Add a new authentication middleware to src/auth.ts that validates JWT tokens. The middleware should check the Authorization header, verify the token, and attach the user to the request object.
-
-**Skill Applied:** using-quality-gates
-
----
-
-## Response (with skill active)
-
-To add the authentication middleware, we need to follow the **TDD workflow** enforced by Quality Gates:
-
-### Step 1: Write a Failing Test First
-
-Before implementing the middleware, you need to write a test that will fail without the implementation. The TDD Guard will block implementation until a failing test exists.
-
-**Create** `src/auth.test.ts` or add to existing test file:
-
-```typescript
-import { authMiddleware } from './auth';
-
-describe('authMiddleware', () => {
-  it('should reject requests without Authorization header', async () => {
-    const req = { headers: {} } as Request;
-    const next = vi.fn();
-    
-    await authMiddleware(req, {} as Response, next);
-    
-    expect(next).not.toHaveBeenCalled();
-  });
-
-  it('should attach user to request with valid JWT', async () => {
-    const token = generateValidToken(); // your test helper
-    const req = { headers: { authorization: `Bearer ${token}` } } as Request;
-    const next = vi.fn();
-    
-    await authMiddleware(req, {} as Response, next);
-    
-    expect(next).toHaveBeenCalled();
-    expect(req.user).toBeDefined();
-  });
-});
-```
-
-Run tests to confirm they fail:
-```bash
-npm test  # or: npx vitest run
-```
-
-### Step 2: Implement the Middleware
-
-Once tests are failing, TDD Guard will allow implementation:
-
-```typescript
-// src/auth.ts
-import jwt from 'jsonwebtoken';
-
-export async function authMiddleware(req: Request, res: Response, next: NextFunction) {
-  const authHeader = req.headers.authorization;
-  
-  if (!authHeader?.startsWith('Bearer ')) {
-    res.status(401).json({ error: 'No token provided' });
-    return;
-  }
-  
-  const token = authHeader.substring(7);
-  
-  try {
-    const decoded = jwt.verify(token, process.env.JWT_SECRET!);
-    (req as any).user = decoded;
-    next();
-  } catch (err) {
-    res.status(401).json({ error: 'Invalid token' });
-  }
-}
-```
-
-### Step 3: Quality Gate Validation
-
-After editing `src/auth.ts`, the **TypeScript Quality Gate** will automatically run:
-- **TypeScript compilation** - Checks types
-- **ESLint** - Validates code style (auto-fixes if enabled)
-- **Prettier** - Formats code (auto-fixes if enabled)
-
-If any issues are found, you'll see error output. Fix remaining issues manually (type errors can't be auto-fixed).
-
-### Step 4: Verify Tests Pass
-
-```bash
-npm test  # All tests should now pass
-```
-
----
-
-**Note:** Ensure you have the required dependencies installed:
-- `npm install --save-dev tdd-guard-vitest` (for Vitest test reporter)
-- `npm install --save-dev typescript eslint prettier` (for quality gate)

package/.xtrm/skills/default/sync-docs/evals/evals.json

@@ -1,89 +0,0 @@
-{
-  "skill_name": "sync-docs",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I just closed a bunch of bd issues this sprint and merged 3 PRs. The README.md is getting long — can you sync the docs and make sure everything's in order? Use sync-docs.",
-      "expected_output": "Runs context_gatherer.py and doc_structure_analyzer.py, reports what was found (closed issues, PRs, any drift), identifies README extraction candidates or MISSING docs/ files, and either fixes them or gives a clear plan with next steps.",
-      "files": [],
-      "assertions": [
-        {
-          "id": "ran-context-gatherer",
-          "description": "Ran context_gatherer.py and reported bd closed issues or merged PRs from the output",
-          "check": "result.md mentions context_gatherer or bd closed issues or merged PRs with specific data"
-        },
-        {
-          "id": "ran-structure-analyzer",
-          "description": "Ran doc_structure_analyzer.py and used its output to identify doc issues",
-          "check": "result.md references MISSING, STALE, EXTRACTABLE, or BLOATED status from the analyzer"
-        },
-        {
-          "id": "concrete-action",
-          "description": "Produced at least one concrete recommendation or action (not just a vague summary)",
-          "check": "result.md names a specific file (e.g. docs/hooks.md) or section with a specific next step"
-        },
-        {
-          "id": "used-skill-scripts",
-          "description": "Used the skill scripts rather than just reading files manually",
-          "check": "result.md shows script execution output, not just manual file reading"
-        }
-      ]
-    },
-    {
-      "id": 2,
-      "prompt": "Run sync-docs --fix on this project and remember what you did with bd.",
-      "expected_output": "Runs doc_structure_analyzer.py --fix --bd-remember, creates scaffold files for any missing docs/ subsystems, persists a bd memory with the summary, then validates the created files with validate_doc.py.",
-      "files": [],
-      "assertions": [
-        {
-          "id": "ran-fix-flag",
-          "description": "Ran doc_structure_analyzer.py with --fix flag",
-          "check": "result.md shows the --fix command was executed"
-        },
-        {
-          "id": "ran-bd-remember",
-          "description": "Ran with --bd-remember or manually ran bd remember with a summary",
-          "check": "result.md shows bd remember was called and reports the memory key"
-        },
-        {
-          "id": "scaffold-created",
-          "description": "At least one scaffold file was created in docs/",
-          "check": "result.md lists a docs/*.md file created, OR reports no gaps found (valid outcome)"
-        },
-        {
-          "id": "validated-schema",
-          "description": "Ran validate_doc.py on created files to confirm schema",
-          "check": "result.md shows validate_doc.py was run and reports pass/fail for created files"
-        }
-      ]
-    },
-    {
-      "id": 3,
-      "prompt": "Do a doc audit. I think the README has sections that should be in docs/ but I'm not sure which ones.",
-      "expected_output": "Runs the full 5-phase sync-docs workflow: gathers context, runs drift detection, runs doc_structure_analyzer.py, and identifies EXTRACTABLE/BLOATED sections with specific suggestions for what goes in which docs/ file before recommending or making changes.",
-      "files": [],
-      "assertions": [
-        {
-          "id": "ran-analyzer",
-          "description": "Ran doc_structure_analyzer.py and referenced its structured output",
-          "check": "result.md cites the analyzer output (EXTRACTABLE, BLOATED, line count, or specific section names from the report)"
-        },
-        {
-          "id": "named-specific-sections",
-          "description": "Named specific README sections with their suggested docs/ destination",
-          "check": "result.md lists at least 2 specific sections (e.g. '## Policy System → docs/policies.md') not just generic advice"
-        },
-        {
-          "id": "actionable-report",
-          "description": "Report is actionable — tells user exactly what to do next, not just observations",
-          "check": "result.md includes a prioritized list or clear next steps, not just 'the README could be shorter'"
-        },
-        {
-          "id": "no-edits-made",
-          "description": "Did not edit or create any files (audit only)",
-          "check": "result.md does not claim to have modified README.md or created docs/ files"
-        }
-      ]
-    }
-  ]
-}

package/.xtrm/skills/default/test-planning/evals/evals.json

@@ -1,23 +0,0 @@
-{
-  "skill_name": "test-planning",
-  "evals": [
-    {
-      "id": 1,
-      "prompt": "I've got an epic for a new notification service (notif-3a). I just created 8 child issues: .1 is the Postgres schema migration, .2 is the async message consumer (reads from RabbitMQ), .3 is the template renderer (Jinja2, pure python), .4 is the delivery client (calls Twilio/SendGrid APIs), .5 is the REST API for managing preferences, .6 is the CLI tool for ops to send test notifications, .7 is the retry/dead-letter handler, .8 is the rate limiter. Break down what testing each of these needs and create the bd issues.",
-      "expected_output": "Should detect layers: .1 (boundary/DB), .2 (boundary/MQ), .3 (core/pure), .4 (boundary/external API), .5 (boundary/API), .6 (shell/CLI), .7 (core/state machine), .8 (core/algorithm). Should batch into ~3 test issues: core tests (.3, .7, .8), boundary/contract tests (.1, .2, .4, .5), shell integration (.6). Should use property-based for rate limiter, contract tests for external APIs, characterization or spec-first for DB schema.",
-      "files": []
-    },
-    {
-      "id": 2,
-      "prompt": "I just finished implementing the data ingestion pipeline (issue data-pipe-9f.4) — it reads CSVs from S3, validates schemas, transforms column types, and writes to Postgres. The parent epic is data-pipe-9f. Can you close it for me? bd close data-pipe-9f.4 --reason 'pipeline implemented and deployed'",
-      "expected_output": "Should trigger closure gate behavior: check bd children data-pipe-9f for existing test issues. Since none exist, should create a test issue covering all layers: unit tests for schema validation and column transforms (core), contract tests for S3 reads and Postgres writes (boundary), integration test for end-to-end pipeline (shell). Should NOT just close the issue without checking for test coverage.",
-      "files": []
-    },
-    {
-      "id": 3,
-      "prompt": "We have an epic tracker-7b with 5 implementation issues done and 1 test issue (tracker-7b.6) that was created during planning. But during implementation of .3 (the websocket price feed handler), we discovered the feed sometimes sends malformed JSON that the parser needs to handle gracefully, and .5 (the position calculator) ended up also doing margin calculations which weren't in the original plan. Can you review tracker-7b.6 and update it?",
-      "expected_output": "Should read tracker-7b.6, identify drift: (1) malformed JSON handling in websocket parser is a new edge case — add property-based tests for parser robustness, (2) margin calculations in position calculator are new core logic — add unit tests. Should update the existing test issue via bd update or bd comments, not create a new one. Should note that the parser needs characterization tests if there's existing behavior to preserve.",
-      "files": []
-    }
-  ]
-}