audit

Audit Strapi frontend files for code quality and generate a structured report.

2|3|Updated May 19, 2022
One-click install
npx skills add https://github.com/SKLINET/strapi-boilerplate --skill audit-sklinet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/SKLINET/strapi-boilerplate/tree/main/.cursor/skills/audit
Command: npx skills add https://github.com/SKLINET/strapi-boilerplate --skill audit-sklinet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an informational audit checklist and produces a structured report for frontend code or components without making changes unless explicitly requested.

Core Features & Use Cases

  • Generates a comprehensive audit report identifying code quality issues, style inconsistencies, and architectural concerns.
  • Distinguishes informational findings from actionable recommendations to guide the user in making targeted improvements.
  • Applies to the Strapi frontend monorepo (frontend/ Next.js) to assess selected files or components and produce a reproducible report suitable for review.

Quick Start

Run the audit to generate an informational audit report for the frontend codebase.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit React and TypeScript code quality without modifying files?

To audit React and TypeScript code quality without modifying files, run a read-only analysis that checks Prettier formatting, TypeScript usage, naming conventions, and React patterns, generating a structured informational report of all findings.

What is included in a frontend code audit report for a Next.js monorepo?

A frontend code audit report for a Next.js monorepo includes informational findings on code style, architecture, and best practices, clearly separating read-only observations from actionable recommendations for targeted improvements.

Can I check file organization and React patterns in selected components only?

Yes, you can check file organization and React patterns in selected components only by applying the audit scope to specific files within the frontend monorepo, producing a reproducible report for just those targeted areas.

Does the audit process automatically fix Prettier formatting and TypeScript issues?

No, the audit process does not automatically fix Prettier formatting and TypeScript issues. It enforces checks across the codebase to identify style inconsistencies and architectural concerns, outputting an informational report without applying any code changes.