security
Run security audit with GitLeaks pre-commit hook setup and code analysis
What this skill does
You are a security engineer setting up GitLeaks and running security audits. ## Workflow ### 1. Setup GitLeaks in Husky Pre-commit Hook Check if GitLeaks is configured in the project's pre-commit hook. If not, set it up. #### Detection Steps 1. Check if `.husky/` directory exists 2. Check if `.husky/pre-commit` contains `gitleaks` #### Setup Steps (if GitLeaks is missing) If `.husky/` does not exist: ```bash npx husky init ``` Add GitLeaks to `.husky/pre-commit` BEFORE any lint-staged command: ```bash gitleaks protect --staged --verbose ``` Example `.husky/pre-commit` with lint-staged: ```bash #!/usr/bin/env sh . "$(dirname -- "$0")/_/husky.sh" # Secrets detection - fail fast if secrets found gitleaks protect --staged --verbose # Lint staged files npx lint-staged ``` If the pre-commit file already exists, insert the gitleaks line before `npx lint-staged`. ### 2. Code Security Audit After ensuring GitLeaks is configured, spawn the security-auditor agent to analyze code: ``` Use the Task tool with subagent_type: security-auditor to run a security audit on the codebase. Focus on OWASP Top 10 vulnerabilities, authentication issues, and data protection. ``` ### 3. Retrospective Git History Scan (Optional) Only run this step if the user passes `--scan-history` argument. This is for legacy projects being onboarded to GitLeaks. ```bash gitleaks detect --source . --verbose ``` Report any secrets found in git history with: - File path and line number - Commit where the secret was introduced - Type of secret detected - Remediation steps (rotate the secret, use git-filter-repo to remove from history) ## Output Format 1. **GitLeaks Setup Status**: Whether hooks were already configured or newly set up 2. **Security Audit Findings**: Results from the security-auditor agent 3. **History Scan Results** (if --scan-history): Any secrets found in git history ## Assumptions - GitLeaks is already installed on the system (`brew install gitleaks` or equivalent) - Target projects use Husky + lint-staged (JS/TS stack)
Related in Security
mac-ops
IncludedComprehensive macOS workstation operations — diagnose kernel panics, identify failing drives, audit launchd startup items, decode wake reasons, triage TCC permission denials, manage APFS snapshots, recover from no-boot. Use for: Mac is slow, slow bootup, won't boot, kernel panic, kernel_task hot, mds_stores CPU, photoanalysisd, cloudd, login loop, gray screen, sleep wake failure, drive failing, IO errors, APFS snapshots eating space, Time Machine local snapshots, Spotlight indexing, launchd, LaunchAgent, LaunchDaemon, login items, TCC permissions, Full Disk Access, Screen Recording denied, Gatekeeper, quarantine, com.apple.quarantine, app is damaged, helper tool, /Library/PrivilegedHelperTools, pmset, wake reasons, dark wake, sysdiagnose, panic.ips, DiagnosticReports, configuration profile, MDM profile, remote diagnostics over SSH.
a11y-audit
IncludedRun accessibility audits on web projects combining automated scanning (axe-core, Lighthouse) with WCAG 2.1 AA compliance mapping, manual check guidance, and structured reporting. Output is configurable: markdown report only, markdown plus machine-readable JSON, or markdown plus issue tracker integration. Use this skill whenever the user mentions "accessibility audit", "a11y audit", "WCAG audit", "accessibility check", "compliance scan", or asks to check a web project for accessibility issues. Also trigger when the user wants to verify WCAG conformance or map findings to a specific standard (CAN-ASC-6.2, EN 301 549, ADA/AODA).
erpclaw
IncludedAI-native ERP system with self-extending OS. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting. 413 actions across 14 domains, 43 expansion modules. Constitutional guardrails, adversarial audit, schema migration. Double-entry GL, immutable audit trail, US GAAP.
assess
IncludedAssesses and rates quality 0-10 across multiple dimensions (correctness, maintainability, security, performance, testability, simplicity) with pros/cons analysis. Compares against project conventions and prior decisions from memory. Produces structured evaluation reports with actionable improvement suggestions. Use when evaluating code, designs, architectures, or comparing alternative approaches.
spring-boot-security-jwt
IncludedProvides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.
code-hardcode-audit
IncludedDetect hardcoded values, magic numbers, and leaked secrets. TRIGGERS - hardcode audit, magic numbers, PLR2004, secret scanning.