outfitter-check

Scan codebases for Outfitter Stack compliance and generate severity-ranked reports.

6|1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/outfitter-dev/outfitter --skill outfitter-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: outfitter-check
Source: https://github.com/outfitter-dev/outfitter/tree/main/plugins/outfitter/skills/outfitter-check
Command: npx skills add https://github.com/outfitter-dev/outfitter --skill outfitter-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically scans your codebase for common anti-patterns and Outfitter Stack violations, providing a clear report to improve code quality and maintainability.

Core Features & Use Cases

  • Automated Code Scanning: Detects critical, high, medium, and low severity issues like thrown exceptions, console logging, and hardcoded paths.
  • Compliance Reporting: Generates a structured report detailing violations, their locations, and suggested fixes referencing fieldguide patterns.
  • Migration Validation: Checks for outdated Outfitter package versions and provides guidance for upgrades.
  • Use Case: Integrate this Skill into your pre-commit hooks or CI/CD pipeline to catch potential issues before they reach production, ensuring adherence to Outfitter best practices.

Quick Start

Run the outfitter-check skill to scan the current directory for compliance issues.

Frequently Asked Questions about outfitter-check

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

FAQPage Schema
How do I scan my codebase for anti-patterns and thrown exceptions?

To scan a codebase for anti-patterns and thrown exceptions, you can run an automated compliance check that identifies severity-ranked issues and generates a report with actionable fixes. It detects console usage and hardcoded paths using diagnostic commands.

What is Outfitter Stack compliance checking and how does it work?

Outfitter Stack compliance checking is an automated codebase analysis that identifies anti-patterns like thrown exceptions and hardcoded paths. It works by scanning for violations and generating a structured, severity-ranked report with migration guidance for Outfitter packages.

How do I check for outdated Outfitter package versions and get upgrade guidance?

To check for outdated Outfitter package versions and get upgrade guidance, run a migration validation scan. It utilizes commands like `bunx outfitter upgrade` to detect old packages and provides structured guidance for upgrading to current Outfitter releases.

Can I use automated code review in pre-commit hooks or CI/CD pipelines?

Yes, you can integrate automated compliance scanning into pre-commit hooks or CI/CD pipelines. Running this check catches potential anti-patterns and Outfitter Stack violations before they reach production, ensuring adherence to code quality best practices.

Does the linter detect console logging and hardcoded paths in my code?

Yes, the linter detects console logging and hardcoded paths by scanning the current directory. It identifies these issues as critical, high, medium, or low severity violations and generates a compliance report detailing their locations and suggested fixes.

What is the best way to refactor code and fix compliance violations?

The best way to refactor code and fix compliance violations is to use an automated compliance report. It provides actionable fixes referencing fieldguide patterns and migration guidance, allowing you to systematically resolve identified anti-patterns by severity.