farm-inspect

Run parallel code quality, security, performance, and accessibility audits with linting and tests.

5|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/WynterJones/OpenPaw --skill farm-inspect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: farm-inspect
Source: https://github.com/WynterJones/OpenPaw/tree/main/.claude/skills/farm-inspect
Command: npx skills add https://github.com/WynterJones/OpenPaw --skill farm-inspect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of thoroughly inspecting code for quality, security, performance, and accessibility issues, ensuring a high standard before releases.

Core Features & Use Cases

  • Parallel Audits: Runs multiple audit agents (code quality, security, performance, accessibility) concurrently.
  • Code Linting & Testing: Executes standard linting, testing, and build commands as quality gates.
  • Dead Code Detection: Identifies unused files, dependencies, and exports using Knip.
  • Use Case: Before deploying a new feature, run farm-inspect to catch potential bugs, security vulnerabilities, and performance bottlenecks, ensuring a stable release.

Quick Start

Run a full code inspection with all audit agents in parallel.

Frequently Asked Questions about farm-inspect

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

FAQPage Schema
How do I run a comprehensive code audit for security and performance before release?

Dead code detection identifies unused files, dependencies, and exports using Knip. It runs as part of a comprehensive code inspection to clean up your project alongside parallel security and performance audits.

Can I run accessibility and security audits concurrently during code inspection?

Yes, parallel audits run multiple agents concurrently to check code quality, security, performance, and accessibility. This concurrent execution catches potential bugs and vulnerabilities simultaneously before deployment.

What is the best way to automate quality gates like linting and testing for deployment?

Automating quality gates involves executing standard linting, testing, and build commands automatically. This comprehensive code inspection uses these gates to catch potential bugs and ensure a stable release before deploying new features.

Does this code inspection approach work without specific external dependencies?

Yes, this code inspection approach operates without external dependencies. It performs comprehensive audits for quality, security, performance, and accessibility internally using parallel agents and built-in quality gates.

How do I detect dead code and unused dependencies in my project?

Dead code detection identifies unused files, dependencies, and exports using Knip. It runs as part of a comprehensive code inspection to clean up your project alongside parallel security and performance audits.