branch-auditor-pgpemulisted

Audit a feature branch against origin/main to highlight changes, verify test coverage, and detect potential bugs. Use this skill whenever you need to: - Understand what changed in a branch compared to main - Verify all changes have corresponding unit tests - Detect potential bugs or regressions - Assess merge risk and readiness - Review code quality, formatting, and architecture - Get actionable recommendations for test coverage gaps This is pgpemu-specific: It understands the ESP32-C3 firmware architecture, the comprehensive test suite (252 assertions across 8 test modules), and code review standards from AGENTS.md. The auditor scans the entire codebase—no specificity needed, the unit tests handle verification.
shortcuts/dotfiles · ★ 18 · Testing & QA · score 74

Install: claude install-skill shortcuts/dotfiles

# Branch Auditor for PGPemu ## Overview This skill audits a feature branch against `origin/main` to: 1. **Summarize changes** — Concise breakdown organized by layer/module 2. **Verify test coverage** — Check if changes have corresponding unit tests; **prompt for test plan if missing** 3. **Flag potential bugs** — Identify threading, memory, and architecture issues 4. **Assess merge risk** — Quantified risk score (0-10) based on finding severity 5. **Code review scan** — Validate formatting, naming, and architecture compliance ## Audit Methodology ### 1. Change Inventory - Count files changed, lines added/deleted - Group changes by layer and module - Identify functional impact (feature, bugfix, refactor, etc.) - Note file deletions or major refactors ### 2. Test Coverage Analysis Scan for test file changes matching modified source files. The pgpemu test suite has **252 assertions** across 8 modules: - `test_regression.c` (42) — Critical bug prevention - `test_edge_cases.c` (71) — Boundary conditions - `test_error_handling.c` (37) — Error recovery - `test_settings.c` (20) — Settings logic - `test_config_storage.c` (37) — NVS persistence - `test_handshake_multi.c` (18) — Multi-device connections - `test_nvs_helper.c` (23) — NVS utilities - `cert-test.c` (4) — Certificate validation **Coverage Check:** - Are modified .c/.h files covered by corresponding test_ files? - Were existing tests updated if APIs changed? - Is there a regression test if fixing a bug? **If no test c