cext-review-toolkit

Comprehensive C extension analysis using specialized agents. Use when the user asks to analyze, audit, or review a C extension, find bugs in C extension code, run all checks on an extension, or do a full extension review. Covers refcount safety, error handling, NULL safety, GIL discipline, module state, type slots, ABI compliance, version compatibility, PyErr_Clear auditing, resource lifecycle, and C/Python parity.

Quick health dashboard scoring a C extension across all dimensions. Use when the user asks for a quick overview, health check, status, score, or summary of a C extension's quality.

Find the worst functions to fix first by combining refcount issues, error handling bugs, and complexity scoring. Use when the user asks where to focus review effort, which functions are most dangerous, what to fix first, or wants a prioritized list of hotspots in a C extension.

Extension modernization assessment covering multi-phase init migration, stable ABI adoption, version compatibility, and free-threading readiness. Use when the user asks to modernize an extension, prepare for subinterpreters, migrate to stable ABI, clean up deprecated APIs, or assess migration effort for a C extension.

Use this agent to measure and analyze C code complexity in extension modules, identifying hotspots and suggesting simplifications. <example> User: What are the most complex functions in this extension? Agent: I will run the complexity measurement script, identify hotspots with score >= 5.0, assess inherent vs reducible complexity, correlate with safety findings, and suggest concrete simplifications. </example>

Use this agent to audit error handling correctness in C extension code that calls the Python/C API. <example> User: Check the error handling in my C extension. Agent: I will run the error path scanner, prioritize missing NULL checks and return-without-exception findings, and review extension-specific error patterns like PyErr_Clear misuse and exception clobbering. </example>

Use this agent to audit GIL (Global Interpreter Lock) management in C extension code, including foreign C library interaction and free-threaded Python readiness. <example> User: Check GIL handling in my C extension that wraps a foreign library. Agent: I will run the GIL usage scanner, verify matched Py_BEGIN/END_ALLOW_THREADS pairs, check for Python API calls without the GIL, audit foreign library callback patterns, and assess free-threaded Python readiness. </example>

Use this agent for temporal analysis of a C extension codebase -- finding similar bugs via git history and prioritizing review by churn patterns. <example> User: We just fixed a NULL check bug -- did we miss any similar bugs elsewhere? Agent: I will run the history analyzer, examine recent fix commits for bug patterns, search the entire codebase for structurally similar code, and produce a churn-risk matrix. </example>

Use this agent to audit module initialization and state management in C extension code, including single-phase vs multi-phase init and global state migration. <example> User: Review the module state management in my C extension. Agent: I will run the module state scanner, assess the init style, catalog global PyObject state, check for missing traverse/clear slots, and produce a migration assessment with difficulty rating. </example>