xtrm-tools 2.3.0 → 2.4.1

package/project-skills/tdd-guard/.claude/settings.json

@@ -1,38 +0,0 @@
-{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Write|Edit|MultiEdit|TodoWrite|mcp__serena__rename_symbol|mcp__serena__replace_symbol_body|mcp__serena__insert_after_symbol|mcp__serena__insert_before_symbol",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/tdd-guard-pretool-bridge.cjs\"",
-            "timeout": 30
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "tdd-guard --prompt-check",
-            "timeout": 15
-          }
-        ]
-      }
-    ],
-    "SessionStart": [
-      {
-        "hooks": [
-          {
-            "type": "command",
-            "command": "tdd-guard --session-init",
-            "timeout": 5
-          }
-        ]
-      }
-    ]
-  }
-}

package/project-skills/tdd-guard/.claude/skills/using-tdd-guard/SKILL.md

@@ -1,79 +0,0 @@
----
-name: using-tdd-guard
-description: TDD Guard enforces Test-Driven Development workflow in Claude Code. Blocks implementation code until failing tests are written.
----
-
-# Using TDD Guard
-
-**TDD Guard** enforces Test-Driven Development workflow in Claude Code. It blocks implementation code until failing tests are written.
-
-## What It Does
-
-- **Blocks Write/Edit** when no failing test exists
-- **Prevents over-implementation** beyond test requirements
-- **Integrates with test reporters** for real-time test status
-
-## How It Works
-
-When you attempt to write implementation code:
-
-1. TDD Guard intercepts the Write/Edit tool call
-2. Checks if a failing test exists (via test reporter JSON)
-3. If no failing test: **blocks the action** with guidance
-4. If failing test exists: **allows** the implementation
-
-## Test Reporters
-
-TDD Guard requires a language-specific test reporter installed in your project:
-
-| Language | Package | Setup |
-|----------|---------|-------|
-| TypeScript/JavaScript (Vitest) | `tdd-guard-vitest` | Add to `vitest.config.ts` |
-| TypeScript/JavaScript (Jest) | `tdd-guard-jest` | Add to `jest.config.ts` |
-| Python (pytest) | `tdd-guard-pytest` | Add to `conftest.py` |
-| PHP (PHPUnit) | `tdd-guard-phpunit` | Add to `phpunit.xml` |
-| Go | `tdd-guard-go` | Run with `go test` wrapper |
-| Rust | `tdd-guard-rust` | Run with `cargo nextest` |
-
-## Example: Vitest Setup
-
-```bash
-# Install reporter
-npm install --save-dev tdd-guard-vitest
-```
-
-```typescript
-// vitest.config.ts
-import { defineConfig } from 'vitest/config'
-import { VitestReporter } from 'tdd-guard-vitest'
-
-export default defineConfig({
-  test: {
-    reporters: [
-      'default',
-      new VitestReporter('/absolute/path/to/your/project'),
-    ],
-  },
-})
-```
-
-## Commands
-
-- `tdd-guard check` - Verify failing test exists (called by hook)
-- `tdd-guard status` - Show current TDD state
-- `tdd-guard session-init` - Initialize session
-
-## Troubleshooting
-
-**"No failing test found"**
-- Write a test that fails first
-- Ensure test reporter is installed and configured
-- Check test reporter JSON output path
-
-**"tdd-guard command not found"**
-- Install globally: `npm install -g tdd-guard`
-
-## See Also
-
-- Full documentation: `.claude/docs/tdd-guard-readme.md`
-- Original repo: https://github.com/nizos/tdd-guard

package/project-skills/tdd-guard/CLAUDE.md

@@ -1,98 +0,0 @@
-# TDD Guard
-
-## Project Goal
-
-TDD Guard is a Claude Code hook that enforces Test-Driven Development by intercepting file operations.
-When Claude Code attempts to edit or write files, TDD Guard:
-
-1. **Captures**: Intercepts Edit, MultiEdit, and Write operations
-2. **Analyzes**: Examines test results, file paths, and code changes
-3. **Validates**: Checks TDD compliance using an AI model
-4. **Blocks**: Prevents operations that skip tests or over-implement
-5. **Guides**: Explains violations and suggests corrections
-
-This automated enforcement maintains code quality without cluttering prompts with TDD reminders.
-
-## Development Workflow
-
-### Commit Guidelines
-
-- **Atomic commits**: Each commit represents one logical change with its tests
-- **Test and implementation together**: Never separate tests from the code they test
-- **Explain why, not what**: Commit messages should explain the reason for the change
-- **Conventional format**: Use prefixes to categorize changes: feat, fix, refactor, test, chore, docs
-
-Example: `feat: add network request filtering to reduce noise in captured data` (explains why, not just what)
-
-## Project Structure
-
-The codebase is organized with core functionality in src/ and language-specific reporters:
-
-```
-reporters/                        # Language-specific test reporters
-├── go/                           # tdd-guard-go - Go test reporter
-├── jest/                         # tdd-guard-jest - Jest reporter (npm)
-├── phpunit/                      # tdd-guard/phpunit - PHPUnit reporter (composer)
-├── pytest/                       # tdd-guard-pytest - Pytest reporter (pip)
-├── rspec/                        # tdd-guard-rspec - RSpec reporter (gem)
-├── rust/                         # tdd-guard-rust - Rust test reporter (crates.io)
-├── storybook/                    # tdd-guard-storybook - Storybook test-runner reporter (npm)
-├── test/                         # Shared test artifacts and integration tests
-└── vitest/                       # tdd-guard-vitest - Vitest reporter (npm)
-
-src/                              # Main CLI application
-├── cli/                          # Hook entry point and context builder
-├── config/                       # Configuration management
-├── contracts/                    # Types and Zod schemas
-├── guard/                        # Guard enable/disable management
-├── hooks/                        # Claude Code hook parsing and processing
-├── linters/                      # ESLint integration for code quality
-├── processors/                   # Test result and lint processing
-├── providers/                    # Model and linter client factories
-├── storage/                      # Storage abstractions
-├── validation/                   # TDD principle validation
-│   ├── validator.ts              # Sends context to AI model and parses response
-│   ├── context/                  # Formats operations for AI validation
-│   ├── prompts/                  # TDD validation rules and AI instructions
-│   └── models/                   # Claude SDK and Anthropic API clients
-└── index.ts                      # Package entry point
-
-test/                             # Main test suite (hooks, integration, utils)
-docs/                             # Documentation (ADRs, configuration, etc.)
-```
-
-### Architecture
-
-TDD Guard is organized as a TypeScript project with integrated language-specific reporters:
-
-- **src/**: Core functionality including contracts, config, storage, and validation
-- **reporters/**: Language-specific test reporters (go, jest, phpunit, pytest, rspec, rust, storybook, vitest)
-- **test/**: Comprehensive test suite with integration tests and utilities
-
-### Testing
-
-#### Guidelines
-
-- **Use test helpers**: Extract setup logic into helper functions placed at the bottom of test files
-- **Use test factories**: Always use factories from `test/utils/` instead of creating data inline
-- **Group tests effectively**: Use `describe` blocks and `beforeEach` for common setup
-- **Keep tests concise**: Keep as little logic in the tests themselves as possible
-
-#### Commands
-
-```bash
-npm run build             # Build main package and workspace reporters (jest, storybook, vitest)
-npm run test              # All unit tests and base integration tests
-npm run test:unit         # Fast unit tests only
-npm run test:reporters    # Test all reporter implementations
-npm run lint              # Check code style and quality
-npm run format            # Auto-format code with Prettier
-npm run checks            # Run all checks: typecheck, lint, format, and test
-```
-
-### Key Design Principles
-
-- **Interface-driven**: Core functionality defined by interfaces (`Storage`, `ModelClient`)
-- **Dependency injection**: Components receive dependencies as parameters
-- **Single responsibility**: Each module has one clear purpose
-- **Type safety**: Comprehensive TypeScript types with runtime validation

package/project-skills/tdd-guard/CONTRIBUTING.md

@@ -1,38 +0,0 @@
-# Contributing
-
-Thank you for your interest in contributing to TDD Guard. Contributions of all kinds are welcome and appreciated, whether it's fixing a bug, improving documentation, or proposing a new feature.
-
-These guidelines exist to help your contributions land smoothly and increase the chances of your work being merged quickly.
-
-## Before You Start
-
-If you'd like to add a feature, add a reporter, change existing behavior, or make a significant refactor, please open an issue first so we can discuss the approach together. This helps us align on direction early and avoids situations where you invest significant effort on something that may not fit the project's current priorities.
-
-Bug fixes and small improvements are welcome as direct pull requests, though opening an issue first is still appreciated so we can track the change.
-
-## Pull Requests
-
-Each pull request should address a single concern. A PR that fixes a bug should not also refactor unrelated code or update formatting elsewhere. If you find additional changes worth making along the way, please open a separate PR for those.
-
-Use meaningful titles that describe what the change accomplishes. The description should explain what the PR introduces and why. For significant design decisions, include an [Architecture Decision Record](docs/adr/).
-
-### Core Requirements
-
-Implementation must be test driven with all relevant and affected tests passing. Run linting and formatting (`npm run checks`) and ensure the build succeeds (`npm run build`).
-
-### Commit Messages
-
-Use conventional commits and communicate the why, not just what. Focus on the reasoning behind changes rather than describing what was changed.
-
-### Reporter Contributions
-
-Project root path can be specified so that tests can be run from any directory in the project. For security, validate that the project root path is absolute and that it is the current working directory or an ancestor of it. Relevant cases must be added to reporter integration tests.
-
-## Style Guidelines
-
-No emojis in code or documentation. Avoid generic or boilerplate content. Be deliberate and intentional. Keep it clean and concise.
-
-## Development
-
-- [Development Guide](DEVELOPMENT.md) - Setup instructions and testing
-- [Dev Container setup](.devcontainer/README.md) - Consistent development environment

package/project-skills/tdd-guard/DEVELOPMENT.md

@@ -1,127 +0,0 @@
-# Development Guide
-
-## Prerequisites
-
-### Main Tests
-
-- Node.js 22+ and npm
-
-### Reporter Tests
-
-- Node.js 22+ and npm
-- Python 3.8+ (for pytest reporter)
-- PHP 8.1+ and Composer (for PHPUnit reporter)
-- Go 1.21+ (for Go reporter)
-- Ruby 2.7+ and Bundler (for RSpec reporter)
-- Rust 1.70+ and Cargo (for Rust reporter)
-- Storybook <= 9.x (for Storybook reporter)
-
-## Using Dev Containers
-
-For a consistent development environment with all dependencies pre-installed, see the [devcontainer setup guide](.devcontainer/README.md).
-
-## Building
-
-Before running tests, install dependencies and build the TypeScript packages:
-
-```bash
-# Install dependencies
-npm install
-
-# Build the main package and all workspaces
-npm run build
-```
-
-## Running Main Tests
-
-The main test suite covers the core TDD Guard functionality:
-
-```bash
-# Run all tests
-npm test
-
-# Run unit tests only (faster)
-npm run test:unit
-
-# Run integration tests
-npm run test:integration
-```
-
-## Running Reporter Tests
-
-Reporter tests verify the language-specific test result collectors.
-
-### Setup
-
-First, install the language-specific dependencies:
-
-```bash
-# Install PHPUnit dependencies
-composer install -d reporters/phpunit
-
-# Set up Python virtual environment and install pytest
-python3 -m venv reporters/pytest/.venv
-reporters/pytest/.venv/bin/pip install -e reporters/pytest pytest
-
-# Build Go reporter
-go build -C reporters/go ./cmd/tdd-guard-go
-
-# Install RSpec dependencies
-bundle install --gemfile=reporters/rspec/Gemfile
-
-# Build Rust reporter
-cargo build --release --manifest-path reporters/rust/Cargo.toml
-```
-
-### Running Tests
-
-```bash
-# Run all reporter tests
-npm run test:reporters
-```
-
-## Code Quality
-
-The project uses ESLint, Prettier, and TypeScript for code quality:
-
-```bash
-# Run all checks (typecheck, lint, format, test)
-npm run checks
-
-# Individual commands
-npm run typecheck      # Type checking
-npm run lint           # Lint and auto-fix
-npm run format         # Format code with Prettier
-```
-
-## Troubleshooting
-
-### PHPUnit Issues
-
-If you get composer errors:
-
-- Ensure PHP 8.1+ is installed: `php --version`
-- Ensure Composer is installed: `composer --version`
-
-### Python/pytest Issues
-
-If you get Python errors:
-
-- Ensure Python 3.8+ is installed: `python3 --version`
-- On some systems, you may need to install python3-venv: `sudo apt install python3-venv`
-
-### Ruby/RSpec Issues
-
-If you get Ruby errors:
-
-- Ensure Ruby 2.7+ is installed: `ruby --version`
-- Ensure Bundler is installed: `bundle --version`
-- If Bundler is missing: `gem install bundler`
-
-### Rust Issues
-
-If you get Rust errors:
-
-- Ensure Rust 1.70+ is installed: `rustc --version`
-- Ensure Cargo is installed: `cargo --version`
-- If Rust is missing: Install from [rustup.rs](https://rustup.rs/)

package/project-skills/tdd-guard/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2025 Nizar Selander
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.