Menu
Run benchmark tests for the type_enforced package. Use when asked to evaluate performance changes or compare different implementations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add or extend a test for type_enforced. Use when asked to write a test, add test coverage, or verify new type_enforced behavior.
Modify code for type enforced. Use when asked to change code, refactor, or implement new functionality.
Format type_enforced/ and test/ with autoflake + black. Use when asked to format, lint, clean up style, prettify, or before committing Python changes.
Release checklist for type_enforced (version bump, docs regeneration, build, publish). Owner-only — do not execute; use this when asked to cut a release, bump the version, generate docs, or publish to PyPI, to explain why you're stopping instead.
Run the type_enforced test suite via nox (all supported Python versions) or pytest (local venv). Use when asked to run tests, verify changes, or check CI-equivalent behavior.
| name | benchmark |
| description | Run benchmark tests for the type_enforced package. Use when asked to evaluate performance changes or compare different implementations. |
Take note of current benchmark results in benchmark.md. Assume this is the current state of the codebase.
Run:
uv run utils/benchmark.py
Consider the new content in benchmark.md and compare it to the previous results. If the new results are worse, consider optimizing the code or reverting changes. If noticibly different, when you report to the user include this information and provide relevant details.