sop-compliance-audit

Audit React codebases for SOP violations and generate compliance reports.

Updated Mar 18, 2025
One-click install
npx skills add https://github.com/utsavm81098/88-residences --skill sop-compliance-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sop-compliance-audit
Source: https://github.com/utsavm81098/88-residences/tree/main/.agents/skills/sop-compliance-audit
Command: npx skills add https://github.com/utsavm81098/88-residences --skill sop-compliance-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The SOP compliance audit skill automatically checks a React codebase against the React.js Internal Coding Standard (SOP) and produces a comprehensive compliance report.

Core Features & Use Cases

  • File Naming Audit: identifies non-kebab-case file names across src.
  • Store Access Audit: flags direct Redux store access in UI components.
  • Logging Audit: detects dangerous or extraneous console usage in production code.
  • Security & Safety Checks: flags dangerouslySetInnerHTML or potential XSS vectors.
  • Architecture & Boundaries: verifies presence of an Error Boundary and folder structure consistency.
  • Configuration Consistency: checks for required config files and engines field in package.json.

Quick Start

Run the SOP audit workflow to generate the current project's compliance report.

Frequently Asked Questions about sop-compliance-audit

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

FAQPage Schema
How do I automate React SOP compliance audits for my codebase?

Automate React SOP compliance audits by scanning the src/ directory to identify violations in naming conventions, Redux store access, console usage, and dangerouslySetInnerHTML patterns, producing a structured compliance report.

What is the best way to check for dangerouslySetInnerHTML and XSS vectors in React?

Check for dangerouslySetInnerHTML and XSS vectors in React by running a static code analysis audit that flags potential security vulnerabilities and provides clear remediation guidance within a structured report.

Can I use static analysis to enforce file naming conventions and folder structure in React?

Yes, static analysis can enforce file naming conventions and folder structure in React by auditing src/ for non-kebab-case file names, verifying Error Boundary presence, and checking folder structure consistency.

How do I detect direct Redux store access in UI components during a code review?

Detect direct Redux store access in UI components by applying static review checks that scan the codebase against internal coding standards and flag boundary violations in a structured compliance report.

Does the React SOP compliance audit check for required configuration files in package.json?

Yes, the React SOP compliance audit checks configuration consistency by verifying the presence of required config files and validating the engines field within package.json during the static review process.

What are the limitations of using a static review for React security practices and console usage?

Static review for React security practices and console usage is limited to identifying predefined SOP violations like extraneous logging and dangerous HTML patterns without executing runtime code or detecting dynamic behavioral flaws.