audit

Audit SvelteKit and PocketBase hooks for lint, type, and pattern risks.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jluckyiv/rivcomocktrial --skill audit-jluckyiv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/jluckyiv/rivcomocktrial/tree/main/.claude/skills/audit
Command: npx skills add https://github.com/jluckyiv/rivcomocktrial --skill audit-jluckyiv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit rivcomocktrial's codebase to identify quality and security risks across the SvelteKit frontend and PocketBase backend hooks, enabling faster remediation.

Core Features & Use Cases

  • Lint and type-check the codebase to surface issues early.
  • Grep for anti-patterns and architectural concerns, then compile a findings brief for PRs or releases.

Quick Start

Run a codebase audit and generate a concise findings brief for the current PR.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I audit a SvelteKit and PocketBase codebase for quality and security risks?

A codebase audit identifies quality and security risks across your SvelteKit frontend and PocketBase backend hooks. It runs deterministic lint, type checks, and pattern greps to surface architectural concerns early, producing a structured findings report for immediate remediation.

What is the best way to run lint and type checks on PR-scoped changes before a release?

The best way to run lint and type checks on PR-scoped changes is to scope the audit to the current pull request. This enforces deterministic checks and greps for anti-patterns within web/src and backend/pb_hooks, delivering a clean second opinion for your release.

Can I use grep to find architectural anti-patterns in PocketBase backend hooks?

Yes, you can use targeted grep searches to find anti-patterns in PocketBase backend hooks. The audit scans backend/pb_hooks for specific code-quality risks and architectural concerns, compiling the results into a concise findings brief for remediation.

Does the codebase audit work on both web and backend directories simultaneously?

Yes, the codebase audit works across both web/src and backend/pb_hooks simultaneously. It applies deterministic lint, type checks, and targeted greps to both directories, producing a single structured findings report covering all code-quality risks.

When should I perform a codebase-wide audit instead of a PR-scoped check?

Perform a codebase-wide audit instead of a PR-scoped check when preparing for a major release or evaluating overall architecture. A full audit scans all web/src and backend/pb_hooks files for anti-patterns, while PR checks focus only on isolated changes.