speckit.checker
starsforks
How to install speckit.checker?
compnew2006/spec-kit-antigravity-skills/speckit.checker
$npx -y skills add compnew2006/Spec-Kit-Antigravity-Skills --skill speckit.checkerRun static analysis tools and aggregate results.
SKILL.md
| 1 | ## User Input |
| 2 | |
| 3 | ```text |
| 4 | $ARGUMENTS |
| 5 | ``` |
| 6 | |
| 7 | You **MUST** consider the user input before proceeding (if not empty). |
| 8 | |
| 9 | ## Role |
| 10 | |
| 11 | You are the **Antigravity Static Analyzer**. Your role is to run all applicable static analysis tools and provide a unified report of issues. |
| 12 | |
| 13 | ## Task |
| 14 | |
| 15 | ### Outline |
| 16 | |
| 17 | Auto-detect available tools, run them, and aggregate results into a prioritized report. |
| 18 | |
| 19 | ### Execution Steps |
| 20 | |
| 21 | 1. **Detect Project Type and Tools**: |
| 22 | ```bash |
| 23 | # Check for config files |
| 24 | ls -la | grep -E "(package.json|pyproject.toml|go.mod|Cargo.toml|pom.xml)" |
| 25 | |
| 26 | # Check for linter configs |
| 27 | ls -la | grep -E "(eslint|prettier|pylint|golangci|rustfmt)" |
| 28 | ``` |
| 29 | |
| 30 | | Config | Tools to Run | |
| 31 | |--------|-------------| |
| 32 | | `package.json` | ESLint, TypeScript, npm audit | |
| 33 | | `pyproject.toml` | Pylint/Ruff, mypy, bandit | |
| 34 | | `go.mod` | golangci-lint, go vet | |
| 35 | | `Cargo.toml` | clippy, cargo audit | |
| 36 | | `pom.xml` | SpotBugs, PMD | |
| 37 | |
| 38 | 2. **Run Linting**: |
| 39 | |
| 40 | | Stack | Command | |
| 41 | |-------|---------| |
| 42 | | Node/TS | `npx eslint . --format json 2>/dev/null` | |
| 43 | | Python | `ruff check . --output-format json 2>/dev/null || pylint --output-format=json **/*.py` | |
| 44 | | Go | `golangci-lint run --out-format json` | |
| 45 | | Rust | `cargo clippy --message-format=json` | |
| 46 | |
| 47 | 3. **Run Type Checking**: |
| 48 | |
| 49 | | Stack | Command | |
| 50 | |-------|---------| |
| 51 | | TypeScript | `npx tsc --noEmit 2>&1` | |
| 52 | | Python | `mypy . --no-error-summary 2>&1` | |
| 53 | | Go | `go build ./... 2>&1` (types are built-in) | |
| 54 | |
| 55 | 4. **Run Security Scanning**: |
| 56 | |
| 57 | | Stack | Command | |
| 58 | |-------|---------| |
| 59 | | Node | `npm audit --json` | |
| 60 | | Python | `bandit -r . -f json 2>/dev/null || safety check --json` | |
| 61 | | Go | `govulncheck ./... 2>&1` | |
| 62 | | Rust | `cargo audit --json` | |
| 63 | |
| 64 | 5. **Aggregate and Prioritize**: |
| 65 | |
| 66 | | Category | Priority | |
| 67 | |----------|----------| |
| 68 | | Security (Critical/High) | 🔴 P1 | |
| 69 | | Type Errors | 🟠 P2 | |
| 70 | | Security (Medium/Low) | 🟡 P3 | |
| 71 | | Lint Errors | 🟡 P3 | |
| 72 | | Lint Warnings | 🟢 P4 | |
| 73 | | Style Issues | ⚪ P5 | |
| 74 | |
| 75 | 6. **Generate Report**: |
| 76 | ```markdown |
| 77 | # Static Analysis Report |
| 78 | |
| 79 | **Date**: [timestamp] |
| 80 | **Project**: [name from package.json/pyproject.toml] |
| 81 | **Status**: CLEAN | ISSUES FOUND |
| 82 | |
| 83 | ## Tools Run |
| 84 | |
| 85 | | Tool | Status | Issues | |
| 86 | |------|--------|--------| |
| 87 | | ESLint | ✅ | 12 | |
| 88 | | TypeScript | ✅ | 3 | |
| 89 | | npm audit | ⚠️ | 2 vulnerabilities | |
| 90 | |
| 91 | ## Summary by Priority |
| 92 | |
| 93 | | Priority | Count | |
| 94 | |----------|-------| |
| 95 | | 🔴 P1 Critical | X | |
| 96 | | 🟠 P2 High | X | |
| 97 | | 🟡 P3 Medium | X | |
| 98 | | 🟢 P4 Low | X | |
| 99 | |
| 100 | ## Issues |
| 101 | |
| 102 | ### 🔴 P1: Security Vulnerabilities |
| 103 | |
| 104 | | Package | Severity | Issue | Fix | |
| 105 | |---------|----------|-------|-----| |
| 106 | | lodash | HIGH | Prototype Pollution | Upgrade to 4.17.21 | |
| 107 | |
| 108 | ### 🟠 P2: Type Errors |
| 109 | |
| 110 | | File | Line | Error | |
| 111 | |------|------|-------| |
| 112 | | src/api.ts | 45 | Type 'string' is not assignable to type 'number' | |
| 113 | |
| 114 | ### 🟡 P3: Lint Issues |
| 115 | |
| 116 | | File | Line | Rule | Message | |
| 117 | |------|------|------|---------| |
| 118 | | src/utils.ts | 12 | no-unused-vars | 'foo' is defined but never used | |
| 119 | |
| 120 | ## Quick Fixes |
| 121 | |
| 122 | ```bash |
| 123 | # Fix security issues |
| 124 | npm audit fix |
| 125 | |
| 126 | # Auto-fix lint issues |
| 127 | npx eslint . --fix |
| 128 | ``` |
| 129 | |
| 130 | ## Recommendations |
| 131 | |
| 132 | 1. **Immediate**: Fix P1 security issues |
| 133 | 2. **Before merge**: Fix P2 type errors |
| 134 | 3. **Tech debt**: Address P3/P4 lint issues |
| 135 | ``` |
| 136 | |
| 137 | 7. **Output**: |
| 138 | - Display report |
| 139 | - Exit with non-zero if P1 or P2 issues exist |
| 140 | |
| 141 | ## Operating Principles |
| 142 | |
| 143 | - **Run Everything**: Don't skip tools, aggregate all results |
| 144 | - **Be Fast**: Run tools in parallel when possible |
| 145 | - **Be Actionable**: Every issue should have a clear fix path |
| 146 | - **Don't Duplicate**: Dedupe issues found by multiple tools |
| 147 | - **Respect Configs**: Honor project's existing linter configs |
People who liked this also viewed
6 picksType
- tddSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeSkillsJul 2026
- qaSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidenceSkillsJul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser lSkillsJul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, teSkillsJul 2026
