run-dev-checks

Execute linting, testing, building, and static analysis checks across languages.

4|1|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/lushly-dev/afd --skill run-dev-checks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-dev-checks
Source: https://github.com/lushly-dev/afd/tree/main/.claude/skills/run-dev-checks
Command: npx skills add https://github.com/lushly-dev/afd --skill run-dev-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the development process by automating crucial checks like linting, testing, building, and static analysis, ensuring code quality and consistency across different languages.

Core Features & Use Cases

  • Language-Aware Commands: Automatically runs the correct linting, testing, and building tools (Ruff for Python, Biome for TypeScript, Clippy for Rust).
  • Quality Gates: Enforces standards for file size, test coverage, and dependency freshness.
  • Static Analysis: Detects dead code, circular imports, and unused dependencies.
  • Use Case: Before committing code, run dev lint to catch style issues, dev test to ensure functionality, and dev_check_size to maintain code readability.

Quick Start

Run the development linting command for the current project.

Frequently Asked Questions about run-dev-checks

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

FAQPage Schema
How do I run linting and static analysis across multiple programming languages?

Automated development checks execute language-aware linting and static analysis by automatically selecting the correct tools, such as Ruff for Python and Clippy for Rust, to ensure consistent code quality across different programming languages.

What are development quality gates and how do they enforce code consistency?

Quality gates enforce code consistency by applying configurable thresholds for file size, test coverage, and dependency freshness, ensuring maintainability and early detection of issues before code integration.

Can I detect dead code and circular imports using automated testing workflows?

Yes, static analysis within the development workflow detects dead code, circular imports, and unused dependencies, addressing the need for comprehensive code structure analysis and early issue detection.

Does this static analysis tool support TypeScript and Rust projects?

Yes, the automated checks support TypeScript and Rust projects by running Biome for TypeScript and Clippy for Rust, alongside Python support with Ruff, to maintain multi-language code quality.

What is the best way to catch style issues and ensure functionality before committing code?

The best way to ensure functionality and catch style issues before committing is to run automated development commands like dev lint for style enforcement and dev test for functionality verification.