crackerjack 0.38.15__tar.gz → 0.39.0__tar.gz

{crackerjack-0.38.15 → crackerjack-0.39.0}/CHANGELOG.md

@@ -5,6 +5,62 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.39.0] - 2025-09-28
+
+### Added
+
+- test: Update 24 files
+
+### Changed
+
+- Crackerjack (quality: 73/100) - 2025-09-25 03:49:18
+- Crackerjack (quality: 73/100) - 2025-09-25 07:28:02
+- Crackerjack (quality: 73/100) - 2025-09-25 07:43:25
+- Crackerjack (quality: 73/100) - 2025-09-25 07:55:55
+- Crackerjack (quality: 73/100) - 2025-09-25 08:27:08
+- Crackerjack (quality: 73/100) - 2025-09-25 11:31:40
+- Crackerjack (quality: 73/100) - 2025-09-26 13:55:31
+- Crackerjack (quality: 73/100) - 2025-09-28 08:40:14
+
+## [Unreleased] - 2025-09-28
+
+### Added
+- feat: add new feature
+
+### Fixed
+- fix: resolve bug in parser
+
+
+## [Unreleased] - 2025-09-28
+
+### Added
+
+- feat: add new feature
+
+### Fixed
+
+- fix: resolve bug in parser
+
+## [Unreleased] - 2025-09-26
+
+### Added
+
+- feat: add new feature
+
+### Fixed
+
+- fix: resolve bug in parser
+
+## [Unreleased] - 2025-09-26
+
+### Added
+
+- feat: add new feature
+
+### Fixed
+
+- fix: resolve bug in parser
+
 ## [0.38.15] - 2025-09-22
 
 ### Changed

{crackerjack-0.38.15 → crackerjack-0.39.0}/CLAUDE.md

@@ -10,359 +10,150 @@ Crackerjack is an opinionated Python project management tool unifying UV, Ruff,
 
 **Clean Code Philosophy**: DRY/YAGNI/KISS - Every line is a liability. Optimize for readability with self-documenting code.
 
-## AI Documentation References
-
-- **[AI-REFERENCE.md](docs/ai/AI-REFERENCE.md)** - Command reference with decision trees
-- **[AGENT-CAPABILITIES.json](AGENT-CAPABILITIES.json)** - Structured agent data
-- **[ERROR-PATTERNS.yaml](ERROR-PATTERNS.yaml)** - Automated issue resolution patterns
-
-## Essential Commands
-
-```bash
-# Daily workflow
-python -m crackerjack                       # Quality checks
-python -m crackerjack --run-tests            # With tests
-python -m crackerjack --ai-fix --run-tests   # AI auto-fixing (recommended)
-
-# Development
-python -m crackerjack --ai-debug --run-tests # Debug AI issues
-python -m crackerjack --skip-hooks           # Skip hooks during iteration
-python -m crackerjack --strip-code           # Code cleaning mode
-
-# Monitoring & Performance
-python -m crackerjack --dashboard            # Comprehensive monitoring dashboard
-python -m crackerjack --unified-dashboard    # Unified real-time dashboard
-python -m crackerjack --monitor              # Multi-project progress monitor
-python -m crackerjack --benchmark            # Run in benchmark mode
-python -m crackerjack --cache-stats          # Display cache statistics
-python -m crackerjack --clear-cache          # Clear all caches
-
-# Server management
-python -m crackerjack --start-mcp-server     # MCP server
-python -m crackerjack --restart-mcp-server   # Restart MCP server
-python -m crackerjack --watchdog             # Monitor/restart services
-
-# Release
-python -m crackerjack --full-release patch  # Full release workflow
-```
-
-## AI Agent System
-
-**9 Specialized Agents** handle domain-specific issues:
-
-- **RefactoringAgent** (0.9): Complexity ≤15, dead code removal
-- **PerformanceAgent** (0.85): O(n²) detection, optimization
-- **SecurityAgent** (0.8): Hardcoded paths, unsafe operations
-- **DocumentationAgent** (0.8): Changelog, .md consistency
-- **TestCreationAgent** (0.8): Test failures, fixtures
-- **DRYAgent** (0.8): Code duplication patterns
-- **FormattingAgent** (0.8): Style violations, imports
-- **ImportOptimizationAgent**: Import cleanup, reorganization
-- **TestSpecialistAgent** (0.8): Advanced testing scenarios
-
-**Usage**: `--ai-fix` enables batch fixing; confidence ≥0.7 uses specific agents
-
-## Advanced Services (Enabled by Default)
-
-Crackerjack now includes sophisticated intelligence services that enhance the development experience automatically:
-
-### 🧠 Smart Commit Messages (Default)
-
-- **AI-Powered Analysis**: Analyzes staged changes using conventional commit patterns
-- **Context-Aware**: Considers file types, change patterns, and scope for descriptive messages
-- **Automatic Detection**: Identifies breaking changes, features, fixes, and refactoring
-- **Fallback Option**: Use `--basic-commit` to disable smart messages when needed
-
-### 📈 Version Intelligence (Integrated)
-
-- **Semantic Analysis**: AI recommends version bumps (major/minor/patch) based on commits
-- **Breaking Change Detection**: Automatically identifies API-breaking changes
-- **Conventional Commits**: Analyzes feat/fix/breaking patterns with confidence scoring
-- **Interactive Mode**: Use `--bump interactive` to see AI recommendations during selection
-
-### 📝 Changelog Automation (Default)
-
-- **Git History Analysis**: Automatically generates changelog entries from commits
-- **Categorized Entries**: Groups changes by type (Added, Fixed, Changed, etc.)
-- **Version Integration**: Updates changelog during version bumps and publishing
-- **Markdown Generation**: Creates properly formatted CHANGELOG.md entries
-
-### 🎯 Quality Intelligence (Active)
-
-- **Anomaly Detection**: ML-based quality trend analysis and early warning system
-- **Pattern Recognition**: Identifies improvement/regression patterns in code quality
-- **Workflow Decisions**: Influences hook selection based on quality history
-- **Predictive Analytics**: Recommends comprehensive vs. fast quality checks intelligently
-
-### ⚡ Performance Benchmarks (Reporting)
-
-- **Real-time Metrics**: Tracks workflow execution time and resource usage
-- **Improvement Analysis**: Shows performance gains from optimizations and caching
-- **Memory Optimization**: Reports cache hit ratios and memory efficiency metrics
-- **Historical Trends**: Maintains performance baselines for comparison
-
-**Integration Benefits**:
-
-- All services work together seamlessly with graceful fallbacks
-- Zero configuration required - intelligent defaults work out of the box
-- Enhanced developer experience with minimal performance impact
-- Comprehensive quality assurance with intelligent automation
-
-## High-Performance Rust Integration
-
-**Ultra-Fast Static Analysis** with seamless Python integration:
-
-- **🦅 Skylos**: Dead code detection **20x faster** than vulture
-- **🔍 Zuban**: Type checking **20-200x faster** than pyright
-- **🚀 Performance**: 6,000+ operations/second throughput
-- **🔄 Compatibility**: Zero breaking changes, drop-in replacements
-
-**Benefits in Daily Workflow**:
-
-- Pre-commit hooks complete in seconds instead of minutes
-- `--run-tests` now blazingly fast with Rust-powered type checking
-- AI agents get faster feedback for more efficient fixing cycles
-- Development iteration speed dramatically improved
-
-## Architecture
-
-**Modular DI Architecture**: `__main__.py` → `WorkflowOrchestrator` → Coordinators → Managers → Services
-
-**Critical Pattern**: Always import protocols from `models/protocols.py`, never concrete classes
-
-```python
-# ❌ Wrong
-from ..managers.test_manager import TestManager
-
-# ✅ Correct
-from ..models.protocols import TestManagerProtocol
-```
-
-**Core Layers**:
-
-- **Orchestration**: `WorkflowOrchestrator`, DI containers, lifecycle management
-- **Coordinators**: Session/phase coordination, async workflows, parallel execution
-- **Managers**: Hook execution (fast→comprehensive), test management, publishing
-- **Services**: Filesystem, git, config, security, health monitoring
-
-## Testing & Development
-
-```bash
-# Specific test
-python -m pytest tests/test_file.py::TestClass::test_method -v
-
-# Coverage
-python -m pytest --cov=crackerjack --cov-report=html
-
-# Custom workers
-python -m crackerjack --run-tests --test-workers 4
-
-# Version bump
-python -m crackerjack --bump patch
-```
-
-## Quality Process
-
-**Workflow Order**:
-
-1. **Fast Hooks** (~5s): formatting, basic checks → retry once if fail
-1. **Full Test Suite**: collect ALL failures, don't stop on first
-1. **Comprehensive Hooks** (~30s): type checking, security, complexity → collect ALL issues
-1. **AI Batch Fixing**: process all collected failures together
-
-**Testing**: pytest with asyncio, 300s timeout, auto-detected workers
-**Coverage**: Ratchet system targeting 100%, never decrease
-
-## Code Standards
-
-**Quality Rules**:
-
-- **Complexity ≤15** per function
-- **No hardcoded paths** (use `tempfile`)
-- **No shell=True** in subprocess
-- **Type annotations required**
-- **Protocol-based DI**
-- **Python 3.13+**: `|` unions, protocols, pathlib
-
-**Refactoring Pattern**: Break complex methods into helpers
-
-```python
-def complex_method(self, data: dict) -> bool:
-    if not self._validate_input(data):
-        return self._handle_invalid_input()
-    processed = self._process_data(data)
-    return self._save_results(processed)
-```
-
-**Critical Regex Safety**: NEVER write raw regex. Use centralized registry:
-
-```python
-# ❌ DANGEROUS
-text = re.sub(r"(\w+) - (\w+)", r"\g < 1 >-\g < 2 >", text)
-
-# ✅ SAFE
-from crackerjack.services.regex_patterns import SAFE_PATTERNS
-
-text = SAFE_PATTERNS["fix_hyphenated_names"].apply(text)
-```
+## CRITICAL SECURITY & QUALITY RULES
 
-## Common Issues & Solutions
-
-**Development**:
-
-- **AI agent ineffective**: Use `--ai-debug --run-tests` for analysis
-- **Import errors**: Always import protocols from `models/protocols.py`
-- **Test hangs**: Avoid complex async tests, use simple synchronous config tests
-- **Coverage failing**: Never reduce below baseline, add tests incrementally
-- **Complexity >15**: Break into helper methods using RefactoringAgent approach
-
-**Server**:
-
-- **MCP not starting**: `--restart-mcp-server` or `--watchdog`
-- **Terminal stuck**: `stty sane; reset; exec $SHELL -l`
-- **Slow tests**: Customize `--test-workers N` or use `--skip-hooks`
-
-## MCP Server Integration
-
-**Features**: Dual protocol (MCP + WebSocket), real-time progress, job tracking
-
-```bash
-# Start server
-python -m crackerjack --start-mcp-server
-
-# Monitor progress at http://localhost:8675/
-python -m crackerjack.mcp.progress_monitor <job_id>
-```
-
-**Available Tools**: `execute_crackerjack`, `get_job_progress`, `get_comprehensive_status`, `analyze_errors`
-
-**Slash Commands**: `/crackerjack:run`, `/crackerjack:status`, `/crackerjack:init`
-
-## Session Management Integration
-
-**Automatic Lifecycle**: Crackerjack projects (git repositories) get automatic session management via session-mgmt-mcp:
-
-- **Session Start**: Automatically initialized when Claude Code connects
-- **Mid-Session**: `/session-mgmt:checkpoint` performs quality checks with intelligent auto-compaction
-- **Session End**: Automatically executed on `/quit`, disconnect, or crash with graceful cleanup
+### 1. NEVER MAKE UNAUTHORIZED CHANGES
 
-**Enhanced Workflow Integration**:
+- **ONLY** modify what is explicitly requested.
+- **NEVER** change unrelated code, files, or functionality.
+- If you think something else needs changing, **ASK FIRST**.
+- Changing anything not explicitly requested is considered **prohibited change**.
 
-```bash
-# Standard crackerjack workflow with automatic session management
-python -m crackerjack --ai-fix --run-tests  # Quality + AI fixing
-# Session checkpoints happen automatically during long runs
-# Session cleanup happens automatically when you quit Claude Code
-```
+### 2. DEPENDENCY MANAGEMENT IS MANDATORY
 
-**Key Features**:
+- **ALWAYS** update package.json/requirements.txt or pyproject.toml when adding imports.
+- **NEVER** add import statements without corresponding dependency entries.
+- **VERIFY** all dependencies are properly declared before suggesting code.
 
-- **Crash Resilience**: Session data preserved through network/system failures
-- **Memory Management**: Auto-compaction during checkpoints when context is heavy
-- **Progress Continuity**: Next session resumes with accumulated learning from previous work
-- **Zero Manual Intervention**: All session lifecycle managed automatically for git repos
+### 3. NO PLACEHOLDERS - EVER
 
-**Manual Override**: Use `/session-mgmt:init`, `/session-mgmt:checkpoint`, `/session-mgmt:end` if needed for fine control
+- **NEVER** use placeholder values like "YOUR_API_KEY", "TODO", or dummy data.
+- **ALWAYS** use proper variable references or configuration patterns.
+- If real values are needed, **ASK** for them explicitly.
+- Use environment variables or config files, not hardcoded values.
 
-**Integration Benefits**:
+### 4. QUESTION VS CODE REQUEST DISTINCTION
 
-- Crackerjack quality metrics tracked over time
-- Test patterns and failure resolutions remembered
-- Error fix strategies learned and suggested
-- Command effectiveness optimized based on history
+- When a user asks a **QUESTION**, provide an **ANSWER** - do NOT change code.
+- Only modify code when explicitly requested with phrases like "change", "update", "modify", "fix".
+- **NEVER** assume a question is a code change request.
 
-## Experimental Features
+### 5. NO ASSUMPTIONS OR GUESSING
 
-**Framework for Future Innovations**: Crackerjack includes a comprehensive experimental features framework designed to safely evaluate and integrate next-generation tools.
+- If information is missing, **ASK** for clarification.
+- **NEVER** guess library versions, API formats, or implementation details.
+- **NEVER** make assumptions about user requirements or use cases.
+- State clearly what information you need to proceed.
 
-### Experimental Hook Framework
+### 6. SECURITY IS NON-NEGOTIABLE
 
-The experimental hook system provides a structured pathway for evaluating new tools before promoting them to stable status:
+- **NEVER** put API keys, secrets, or credentials in client-side code.
+- **ALWAYS** implement proper authentication and authorization.
+- **ALWAYS** use environment variables for sensitive data.
+- **ALWAYS** implement proper input validation and sanitization.
+- **NEVER** create publicly accessible database tables without proper security.
+- **ALWAYS** implement row-level security for database access.
 
-```bash
-# Framework supports experimental evaluation
-python -m crackerjack --experimental-hooks  # (when experimental hooks are available)
-```
+### 7. CAPABILITY HONESTY
 
-**Evaluation Criteria**:
+- **NEVER** attempt to generate images, audio, or other media.
+- If asked for capabilities you don't have, state limitations clearly.
+- **NEVER** create fake implementations of impossible features.
+- Suggest proper alternatives using appropriate libraries/services.
 
-1. **Availability**: Tool consistently available across environments
-1. **Stability**: No crashes or inconsistent results across runs
-1. **Value Added**: Catches issues not found by existing tools
-1. **Performance**: Stays within time budgets
-1. **Integration**: Works reliably with pre-commit workflow
+### 8. PRESERVE FUNCTIONAL REQUIREMENTS
 
-**Promotion Lifecycle**:
+- **NEVER** change core functionality to "fix" errors.
+- When encountering errors, fix the technical issue, not the requirements.
+- If requirements seem problematic, **ASK** before changing them.
+- Document any necessary requirement clarifications.
 
-1. **Experimental Phase**: Limited to `manual` stage only
-1. **Evaluation Period**: 30-90 day assessment with metrics
-1. **Promotion Decision**: Move to appropriate tier if criteria met
-1. **Removal**: Clean removal if criteria not met
+### 9. EVIDENCE-BASED RESPONSES
 
-**Current Status**:
+- When asked if something is implemented, **SHOW CODE EVIDENCE**.
+- Format: "Looking at the code: [filename] (lines X-Y): [relevant code snippet]"
+- **NEVER** guess or assume implementation status.
+- If unsure, **SAY SO** and offer to check specific files.
 
-- **No Active Experimental Hooks**: Previous experimental candidates (pyrefly, ty) failed availability testing and were removed
-- **Framework Ready**: System prepared for future experimental tool evaluation
-- **Documentation**: Complete evaluation criteria in [EXPERIMENTAL-EVALUATION.md](EXPERIMENTAL-EVALUATION.md)
+### 10. NO HARDCODED EXAMPLES
 
-## Critical Reminders
+- **NEVER** hardcode example values as permanent solutions.
+- **ALWAYS** use variables, parameters, or configuration for dynamic values.
+- If showing examples, clearly mark them as examples, not implementation.
 
-**Core Instructions**:
+### 11. INTELLIGENT LOGGING IMPLEMENTATION
 
-- Do only what's asked, nothing more
-- NEVER create files unless absolutely necessary
-- ALWAYS prefer editing existing files
-- MAINTAIN coverage ratchet
+- **AUTOMATICALLY** add essential logging to understand core application behavior.
+- Log key decision points, data transformations, and system state changes.
+- **NEVER** over-log (avoid logging every variable or trivial operations).
+- **NEVER** under-log (ensure critical flows are traceable).
+- Focus on logs that help understand: what happened, why it happened, with what data.
+- Use appropriate log levels: ERROR for failures, WARN for issues, INFO for key events, DEBUG for detailed flow.
+- **ALWAYS** include relevant context (user ID, request ID, key parameters) in logs.
+- Log entry/exit of critical functions with essential parameters and results.
 
-**Quality Standards**:
+## RESPONSE PROTOCOLS
 
-- **Test Quality**: Avoid async tests that hang, use synchronous config tests
-- **Import Compliance**: Use protocols from `models/protocols.py`
-- **Fix failures FIRST** before creating new tests
-- Use IDE diagnostics after implementation
+### When Uncertain:
 
-**Failure Patterns to Avoid**:
+- State: "I need clarification on [specific point] before proceeding."
+- **NEVER** guess or make assumptions.
+- Ask specific questions to get the information needed.
 
-```python
-# ❌ Async tests that hang
-@pytest.mark.asyncio
-async def test_batch_processing(self, batched_saver):
-    await batched_saver.start()  # Can hang
+### When Asked "Are You Sure?":
 
+- Re-examine the code thoroughly.
+- Provide specific evidence for your answer.
+- If uncertain after re-examination, state: "After reviewing, I'm not certain about [specific aspect]. Let me check [specific file/code section]."
+- **MAINTAIN CONSISTENCY** - don't change answers without new evidence.
 
-# ✅ Simple synchronous tests
-def test_batch_configuration(self, batched_saver):
-    assert batched_saver.max_batch_size == expected_size
+### Error Handling:
 
+- **ANALYZE** the actual error message/response.
+- **NEVER** assume error causes (like rate limits) without evidence.
+- Ask the user to share error details if needed.
+- Provide specific debugging steps.
 
-# ❌ Import concrete classes
-from ..managers.test_manager import TestManager
+### Code Cleanup:
 
-# ✅ Import protocols
-from ..models.protocols import TestManagerProtocol
-```
+- **ALWAYS** remove unused code when making changes.
+- **NEVER** leave orphaned functions, imports, or variables.
+- Clean up any temporary debugging code automatically.
 
-**Current Status**: 10.11% coverage baseline targeting 100% (ratchet system: 2% tolerance, never reduce)
+## MANDATORY CHECKS BEFORE RESPONDING
 
-- make sure to run `python -m crackerjack` after every editing/debugging cycle for quality checking
-- always put implementation plans in a md doc for review and reference
-- think when you need to think, think harder when you need to think harder
+Before every response, verify:
 
-# Test debug logging
+- [ ] Am I only changing what was explicitly requested?
+- [ ] Are all new imports added to dependency files?
+- [ ] Are there any placeholder values that need real implementation?
+- [ ] Is this a question that needs an answer, not code changes?
+- [ ] Am I making any assumptions about missing information?
+- [ ] Are there any security vulnerabilities in my suggested code?
+- [ ] Am I claiming capabilities I don't actually have?
+- [ ] Am I preserving all functional requirements?
+- [ ] Can I provide code evidence for any implementation claims?
+- [ ] Are there any hardcoded values that should be variables?
 
-<!-- CRACKERJACK INTEGRATION START -->
+## VIOLATION CONSEQUENCES
 
-# CLAUDE.md
+Violating any of these rules is considered a **CRITICAL ERROR** that can:
 
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+- Break production applications
+- Introduce security vulnerabilities
+- Waste significant development time
+- Compromise project integrity
 
-## Project Overview
+## EMERGENCY STOP PROTOCOL
 
-Crackerjack is an opinionated Python project management tool unifying UV, Ruff, pytest, and pre-commit into a single workflow with AI agent integration via MCP.
+If you're unsure about ANY aspect of a request:
 
-**Key Dependencies**: Python 3.13+, UV, pre-commit, pytest
+1. **STOP** code generation.
+1. **ASK** for clarification.
+1. **WAIT** for explicit confirmation.
+1. Only proceed when 100% certain.
 
-**Clean Code Philosophy**: DRY/YAGNI/KISS - Every line is a liability. Optimize for readability with self-documenting code.
+Remember: It's better to ask for clarification than to make assumptions that could break everything.
 
 ## AI Documentation References
 
@@ -703,5 +494,3 @@ from ..models.protocols import TestManagerProtocol
 - think when you need to think, think harder when you need to think harder
 
 # Test debug logging
-
-<!-- CRACKERJACK INTEGRATION END -->

{crackerjack-0.38.15 → crackerjack-0.39.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: crackerjack
-Version: 0.38.15
+Version: 0.39.0
 Summary: Crackerjack Python project management tool
 Project-URL: documentation, https://github.com/lesleslie/crackerjack
 Project-URL: homepage, https://github.com/lesleslie/crackerjack
@@ -31,6 +31,9 @@ Requires-Dist: hypothesis>=6.100
 Requires-Dist: jinja2>=3.1
 Requires-Dist: keyring>=25.6
 Requires-Dist: mcp>=1.12.2
+Requires-Dist: nltk>=3.9.1
+Requires-Dist: numpy>=2.2.1
+Requires-Dist: onnxruntime>=1.19.0
 Requires-Dist: pre-commit>=4.2
 Requires-Dist: psutil>=6.1.0
 Requires-Dist: pydantic>=2.11.7
@@ -47,12 +50,14 @@ Requires-Dist: pyyaml>=6.0.2
 Requires-Dist: refurb>=2.1
 Requires-Dist: rich>=14.1
 Requires-Dist: ruff>=0.12.9
+Requires-Dist: scikit-learn>=1.6.1
 Requires-Dist: scipy>=1.14.0
 Requires-Dist: skylos>=2.1.2
 Requires-Dist: structlog>=24.4
 Requires-Dist: textual>=0.89
 Requires-Dist: tomli-w>=1.2
 Requires-Dist: tomli>=2.2.1
+Requires-Dist: transformers>=4.21.0
 Requires-Dist: typer>=0.16
 Requires-Dist: types-aiofiles>=24.1.0.20240626
 Requires-Dist: types-psutil>=6.0.0.12
@@ -74,7 +79,7 @@ Description-Content-Type: text/markdown
 [![uv](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json)](https://github.com/astral-sh/uv)
 [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit)](https://github.com/pre-commit/pre-commit)
 [![License](https://img.shields.io/badge/License-BSD%203--Clause-blue.svg)](https://opensource.org/licenses/BSD-3-Clause)
-![Coverage](https://img.shields.io/badge/coverage-18.2%25-red)
+![Coverage](https://img.shields.io/badge/coverage-18.4%25-red)
 
 ## 🎯 Purpose
 

{crackerjack-0.38.15 → crackerjack-0.39.0}/README.md

@@ -7,7 +7,7 @@
 [![uv](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json)](https://github.com/astral-sh/uv)
 [![pre-commit](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit)](https://github.com/pre-commit/pre-commit)
 [![License](https://img.shields.io/badge/License-BSD%203--Clause-blue.svg)](https://opensource.org/licenses/BSD-3-Clause)
-![Coverage](https://img.shields.io/badge/coverage-18.2%25-red)
+![Coverage](https://img.shields.io/badge/coverage-18.4%25-red)
 
 ## 🎯 Purpose