code-sentinel

Anti-patterns are recurring code issues caught by tests. code-sentinel maps each failing test to documented anti-patterns—like grep exit code handling or git operations without staging—and applies root-cause fixes. Re-run pytest to verify the issue is resolved and no new problems appear.

Common anti-patterns include heredocs in GitHub Actions, non-deterministic file selection, fixed window geometry, PyInstaller hidden imports, path case sensitivity issues, and absolute imports for sibling modules. code-sentinel identifies these through pytest and applies documented solutions to address root causes, not just symptoms.

Yes. code-sentinel integrates with CI/CD pipelines using pytest to detect anti-patterns automatically. It maps failures to remediation steps, applies fixes deterministically, and re-runs tests to confirm resolution, preventing regressions without manual intervention.

pytest identifies test failures; code-sentinel goes further by mapping failures to specific documented anti-patterns and applying targeted root-cause fixes rather than leaving failures unresolved. It ensures fixes are deterministic and verified through re-testing.

code-sentinel requires pytest. It works locally during development or in CI/CD pipelines to detect and remediate anti-patterns documented in mapped reference files, with no additional tool dependencies needed.