What problem does it solve? Automotive software teams must enforce ASPICE compliance, MISRA coding rules, AUTOSAR naming conventions, and quality gates consistently, but manual enforcement in code reviews is error-prone and inconsistent. ## Core Features & Use Cases - Pre-commit validation: Runs MISRA-C checks, AUTOSAR naming verification, cyclomatic complexity analysis, license header checks, file size limits, and ASPICE work product traceability on staged files. - Pre-push and pre-merge gates: Enforces code coverage thresholds (line, branch, function), dependency vulnerability audits across npm/pip/Maven/Cargo, breaking API change detection, documentation completeness, and integration test execution. - Post-commit and post-deploy automation: Collects commit metrics into JSONL records and verifies monitoring endpoints, Prometheus scraping, Grafana dashboards, and alert rules after deployment. - Use Case: An automotive ECU firmware team installs these hooks so every commit is automatically checked for MISRA violations and requirements traceability, and every push is blocked if coverage drops below 80% or critical dependency vulnerabilities exist. ## Quick Start Set up the automotive Git hooks from this skill in my repository so that MISRA, AUTOSAR naming, and coverage checks run automatically on commit and push.