mutation-testing 0.1.0__tar.gz

mutation_testing-0.1.0/.claude/skills/markdown-extraction.md

@@ -0,0 +1,172 @@
+# Markdown Section Extraction Skill
+
+Use this skill when you need to extract specific sections from markdown documentation files.
+
+## When to Use This Skill
+
+- User asks about specific sections of project documentation
+- Need to retrieve targeted information from markdown files
+- Want to list available documentation sections
+- Need to extract all sections at a specific heading level
+
+## Available Commands
+
+The `md-extract.sh` script provides three main commands:
+
+### 1. List Headers
+Lists all headers in a markdown file with their line numbers and levels.
+
+```bash
+./md-extract.sh <file.md> list
+```
+
+**Example:**
+```bash
+./md-extract.sh claude.md list
+```
+
+**Output format:**
+```
+123  L1: Project Overview
+145  L2: Core Goals
+167  L3: Runtime Mutation Injection
+```
+
+### 2. Extract Section by Header Name
+Extracts a specific section and all its subsections by header name.
+
+```bash
+./md-extract.sh <file.md> extract "<header-name>"
+```
+
+**Examples:**
+```bash
+# Extract the "Core Goals" section
+./md-extract.sh claude.md extract "Core Goals"
+
+# Extract the "Architecture" section
+./md-extract.sh docs/pytest_mutation_plan.md extract "Architecture"
+
+# Extract nested section
+./md-extract.sh claude.md extract "Runtime Mutation Injection"
+```
+
+**Behavior:**
+- Returns the header and all content until the next header of same or higher level
+- Includes all subsections within the extracted section
+- Case-sensitive header matching
+
+### 3. Extract All Sections at Level
+Extracts all sections at a specific heading level (1-6).
+
+```bash
+./md-extract.sh <file.md> extract-level <1-6>
+```
+
+**Examples:**
+```bash
+# Extract all top-level sections (# headers)
+./md-extract.sh claude.md extract-level 1
+
+# Extract all second-level sections (## headers)
+./md-extract.sh claude.md extract-level 2
+```
+
+## Available Documentation Files
+
+- `claude.md` - Project overview and goals
+- `docs/pytest_mutation_plan.md` - Detailed implementation plan
+- `doc/ast_parsing_guide.md` - AST parsing reference
+- `README.md` - Basic project description
+
+## Usage Patterns
+
+### Pattern 1: User asks about project goals
+```
+User: "What are the goals of this project?"
+
+Agent: Let me extract the goals section from the project documentation.
+[Run: ./md-extract.sh claude.md extract "Core Goals"]
+[Present the extracted content to user]
+```
+
+### Pattern 2: User wants overview of documentation structure
+```
+User: "What documentation is available?"
+
+Agent: Let me list the sections in the main documentation.
+[Run: ./md-extract.sh claude.md list]
+[Present formatted list to user]
+```
+
+### Pattern 3: User asks about specific technical topic
+```
+User: "How does the architecture work?"
+
+Agent: Let me extract the architecture section.
+[Run: ./md-extract.sh claude.md extract "Architecture"]
+[Present the content and answer follow-up questions]
+```
+
+### Pattern 4: User wants all main sections
+```
+User: "Give me an overview of all main topics"
+
+Agent: Let me extract all top-level sections.
+[Run: ./md-extract.sh claude.md extract-level 1]
+[Summarize the sections for the user]
+```
+
+## Implementation Guidelines
+
+1. **Always verify file exists** before running extraction
+2. **Quote header names** when they contain spaces
+3. **Use absolute or relative paths** correctly based on current directory
+4. **Present extracted content** in a readable format to the user
+5. **Offer to extract related sections** if user needs more context
+
+## Error Handling
+
+If a header is not found:
+```
+Error: Header 'X' not found in file.md
+```
+
+Solution: Run `list` command first to see available headers with correct spelling.
+
+If file is not found:
+```
+Error: File 'X' not found
+```
+
+Solution: Check the file path and current working directory.
+
+## Example Session
+
+```
+User: "What's this project about?"
+
+Agent: Let me get the project overview for you.
+
+[Runs: ./md-extract.sh claude.md extract "Project Overview"]
+
+Agent: This is a Python mutation testing framework that validates test suite
+quality by injecting runtime mutations and verifying tests catch them...
+[continues with extracted content]
+
+Would you like me to extract more details about any specific aspect?
+```
+
+## Tips for Best Results
+
+- Start with `list` to see structure if unfamiliar with the file
+- Use `extract` for focused information retrieval
+- Use `extract-level 2` to get an overview of major topics
+- Chain extractions: first get overview, then drill into specific sections
+- Always provide context from the extracted content in your response
+
+## Script Location
+
+The script is located at: `./md-extract.sh` (project root)
+
+Make sure you're in the project root directory when running commands, or use the full path.

mutation_testing-0.1.0/.devcontainer/devcontainer.json

@@ -0,0 +1,15 @@
+{
+  "name": "Development Container",
+  "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
+  "forwardPorts": [
+    6369
+  ],
+  "remoteEnv": {
+    "ANTHROPIC_BASE_URL": "https://openrouter.ai/api",
+    "ANTHROPIC_AUTH_TOKEN": "${localEnv:OR_KEY}",
+    "ANTHROPIC_API_KEY": "",
+    "ANTHROPIC_DEFAULT_OPUS_MODEL": "xiaomi/mimo-v2-flash:free",
+    "ANTHROPIC_DEFAULT_HAIKU_MODEL": "xiaomi/mimo-v2-flash:free",
+    "ANTHROPIC_DEFAULT_SONNET_MODEL": "xiaomi/mimo-v2-flash:free"
+  }
+}

mutation_testing-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,19 @@
+name: Publish to PyPI
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write  # required for trusted publishing
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install build
+      - run: python -m build
+      - uses: pypa/gh-action-pypi-publish@release/v1

mutation_testing-0.1.0/.gitignore

@@ -0,0 +1,207 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+#poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+#pdm.lock
+#pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+#pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Abstra
+# Abstra is an AI-powered process automation framework.
+# Ignore directories containing user credentials, local state, and settings.
+# Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#  Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#  that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#  and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#  you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor
+#  Cursor is an AI-powered code editor. `.cursorignore` specifies files/directories to
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/

mutation_testing-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 YeahWick
+
+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.