skills.rest
jterratsdev
jterratsdevOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Static Analysis

Runs and interprets local lint, typecheck, secret, dependency, and security scans.

Updated Dec 1, 2025
Search Tags:#quality gate#sast#lint#dependency audit#precommit#typecheck#secret scanning
One-click install
npx skills add https://github.com/jterratsdev/smart-deployment --skill static-analysis-jterratsdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Static Analysis
Source: https://github.com/jterratsdev/smart-deployment/tree/main/skills/static-analysis
Command: npx skills add https://github.com/jterratsdev/smart-deployment --skill static-analysis-jterratsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often skip or misrun local quality and security checks before committing code, leading to failed CI pipelines, leaked secrets, and undetected vulnerabilities. This Skill standardizes how lint, typecheck, secret, SAST, and dependency scans are executed and interpreted before handoff or commit. ## Core Features & Use Cases - Guided check execution: Inspects the project's configured checks first, runs the smallest relevant check, then the full gate before commit. - Multi-domain coverage: Handles lint, typecheck, secret scanning, SAST, dependency audits, and precommit hooks. - Evidence-based gating: Records command evidence and treats failed required checks as blockers unless explicitly deferred. - Use Case: Before pushing a feature branch, ask the assistant to run the project's lint and secret scans, interpret any failures, and confirm the branch passes the full quality gate. ## Quick Start Run the configured lint, typecheck, and secret scans on this repository and report any blocking failures before I commit.

Frequently Asked Questions about Static Analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run lint and typecheck before committing code?▼

Inspect the project's configured checks first, then run the smallest relevant check such as lint or typecheck on changed files. Before committing, run the full quality gate and treat any failed required check as a blocker unless explicitly deferred.

What is the best way to scan code for secrets before a commit?▼

Use the project's configured secret scanning check as part of the precommit routine rather than inventing new commands. Run the targeted secret scan first, then the full gate, and record the command output as evidence.

Should I run the full test suite or just targeted checks?▼

Run the smallest relevant check first to get fast feedback on the changed area, then run the full gate before handoff or commit. This ordering catches issues early while still enforcing the complete quality standard.

What happens when a required static analysis check fails?▼

A failed required check is treated as a blocker and should stop the commit or handoff. It can only be bypassed when explicitly deferred, and the failure evidence should be recorded with the command output.

Can this approach handle SAST and dependency vulnerability scans?▼

Yes, the procedure covers SAST and dependency scans alongside lint, typecheck, and secret detection. It relies on whatever checks are already configured in the repository rather than introducing new tooling.

Related Skills

Explore More Software Engineering Skills→
Norfolk-GroupNorfolk-Group

ci-hygiene

Detect and repair ESLint, secret-scanner, and TypeScript CI failures in GitHub Actions workflows.

Official
Intermediate
BlackRoad-OS-IncBlackRoad-OS-Inc
1

verification-before-completion

Runs verification commands and reports their outputs before declaring completion.

Official
Intermediate
ssrxsssrxs

laravel-verification

Verifies Laravel projects' environment, code quality, security, and deployment readiness.

Community
Advanced
AmirTlinovAmirTlinov

compas

Validate code quality and enforce standards across repositories with configurable checks.

Community
Advanced