skills.rest
Pact-Community-Organization
Pact-Community-OrganizationOFFICIAL
Explore all skills by this author →
Website𝕏@PactCommOrgGitHub

static-analysis

Detect Pact 5 vulnerabilities and anti-patterns via parse, shadowing, and arity checks.

1|1|Updated Jun 9, 2026
Search Tags:#code-quality#static-analysis#analyze#precommit#shadowing#parse-errors#pact5
One-click install
npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill static-analysis-pact-community-organization
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: static-analysis
Source: https://github.com/Pact-Community-Organization/github-marketplace/tree/main/skills/static-analysis
Command: npx skills add https://github.com/Pact-Community-Organization/github-marketplace --skill static-analysis-pact-community-organization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pact 5 code contains traps and anti-patterns that are hard to spot manually; this skill automates scanning to surface critical issues early.

Core Features & Use Cases

  • Tier 1 real-tooling checks that parse and type modules to catch shadowing, arity, and parse errors.
  • Tier 2 grep-based backstops to catch semantic anti-patterns the compiler might miss.
  • Use Case: integrate into pre-commit workflows to ensure code quality across Pact modules.

Quick Start

Run the static-analysis skill on a Pact module to preemptively identify structural and semantic issues before merging.

Frequently Asked Questions about static-analysis

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

FAQPage Schema
How do I catch shadowing and parse errors in Pact 5 code?▼

Automated static analysis identifies Pact 5 code vulnerabilities by running parse, type, and shadowing checks to surface shadowing and parse errors before merging.

What is the best way to automate code quality checks for Pact modules?▼

Automated static analysis provides Tier 1 tooling and Tier 2 grep backstops to enforce code quality across Pact modules, catching semantic anti-patterns the compiler might miss.

Can I use static analysis in a pre-commit workflow for Pact 5?▼

Yes, static analysis is designed for pre-commit workflows to preemptively identify structural and semantic issues in Pact 5 modules during code review.

How does static analysis detect semantic anti-patterns in Pact 5?▼

Static analysis detects semantic anti-patterns using Tier 2 grep-based backstops that catch semantic anti-patterns the compiler might miss, ensuring robust code quality.

Does Pact 5 static analysis check arity and type errors?▼

Yes, static analysis enforces Tier 1 authoritative tooling to parse and type modules, catching arity and type errors alongside shadowing and parse errors.

Related Skills

Explore More Software Engineering Skills→
Pact-Community-OrganizationPact-Community-Organization
1

formal-verification

Verify Pact modules against model-based properties and invariants.

Official
Advanced
0xHoneyJar0xHoneyJar
1

dapp-lint

Scan dApp frontend code for Web3 anti-patterns using oxlint or eslint.

Official
Advanced
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
Pact-Community-OrganizationPact-Community-Organization
1

pact-security-review

Audit Pact 5 modules for capability and guard vulnerabilities.

Official
Advanced