run-dev-checks — language-aware linting run-dev-checks, afd, lushly-dev, community, language-aware linting, ai agent skill, ide skills, agent automation, automated code testing, static analysis tools, code quality checks, python development tools

v1.0.0
GitHub

About this Skill

Perfect for Code Review Agents needing advanced language-aware linting and testing capabilities for Python, TypeScript, and Rust run-dev-checks is a skill that automates code quality checks, providing language-aware linting, testing, and building capabilities for developers.

Features

Run language-aware commands for Python, TypeScript, and Rust
Validate file sizes, test coverage, and dependency freshness against configurable thresholds
Analyze code structure to find dead code and circular imports
Execute lint, test, and build using the correct tool for the detected language
Perform static analysis for improved code quality
Check code quality gates for consistent development standards

# Core Topics

lushly-dev lushly-dev
[3]
[1]
Updated: 3/16/2026

Quality Score

Top 5%
34
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
> npx killer-skills add lushly-dev/afd/run-dev-checks
Supports 19+ Platforms
Cursor
Windsurf
VS Code
Trae
Claude
OpenClaw
+12 more

Agent Capability Analysis

The run-dev-checks skill by lushly-dev is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for language-aware linting, automated code testing, static analysis tools.

Ideal Agent Persona

Perfect for Code Review Agents needing advanced language-aware linting and testing capabilities for Python, TypeScript, and Rust

Core Value

Empowers agents to execute language-aware commands for linting, testing, and building, while validating code quality against configurable thresholds and analyzing code structure for dead code and circular imports, utilizing tools like language-aware linters and test frameworks

Capabilities Granted for run-dev-checks

Automating code quality checks for Python, TypeScript, and Rust projects
Validating test coverage and dependency freshness against customizable thresholds
Analyzing code structure to identify dead code and circular imports

! Prerequisites & Limits

  • Supports only Python, TypeScript, and Rust languages
  • Requires configuration of thresholds for code quality checks
Project
SKILL.md
5.5 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

Running Dev Checks

Expert guidance for botcore's development command suite — language-aware linting, testing, building, quality gates, and static analysis.

Capabilities

  1. Run Language-Aware Commands -- Execute lint, test, and build using the correct tool for the detected language (Python/TypeScript/Rust)
  2. Check Code Quality -- Validate file sizes, test coverage, and dependency freshness against configurable thresholds
  3. Analyze Code Structure -- Find dead code, circular imports, unused dependencies, and generate dependency graphs
  4. Check Portability -- Detect hardcoded paths that break cross-platform compatibility
  5. Lint Skills -- Validate skill directories against the Agent Skills format specification

Routing Logic

Request TypeLoad Reference
dev_lint, dev_test, dev_build signatures, language dispatchreferences/core-commands.md
dev_check_size, dev_check_coverage, dev_check_deps thresholdsreferences/quality-checks.md
dev_dead_code, dev_circular_imports, dev_unused_deps, dev_dep_graphreferences/analysis.md
Common error codes and resolutionsreferences/troubleshooting.md

Core Principles

1. Lefthook IS the CI Pipeline

<rules> `pnpm check` runs the exact same steps as GitHub Actions CI. If it passes locally, CI passes remotely. The quality gate runs: lint → build → typecheck → test:coverage + portability, file-size, orphan-files. Never add a check to CI without adding it to lefthook's `check` group first. Never add a check to lefthook without verifying CI runs the same command. Drift between local and remote gates is a bug — the `check` group is the single source of truth. </rules>

2. Three Enforcement Layers

LayerWhenSpeedWhat
Pre-commitgit commit~8sLint staged files, portability, file-size, typecheck
Pre-pushgit push~25sFull lint, test, typecheck, portability, file-size, orphan-files
On-demand (pnpm check)Before release / manual~25sSame as pre-push + build + test:coverage

Pre-commit catches formatting. Pre-push catches regressions. pnpm check catches everything CI would catch.

3. Language Dispatch Is Automatic

<rules> Dev commands read the `language`, `linter`, `test_runner`, and `formatter` from config. The same `dev_lint()` call runs ruff for Python, biome for TypeScript, or clippy for Rust. Never hardcode tool names in scripts — let config drive tool selection. </rules>

2. Thresholds Are Config-Driven

<rules> All quality thresholds come from `BotCoreConfig` with sensible defaults. Override per-package in `[tool.botcore.packages.NAME]` for monorepos. </rules>
CheckConfig FieldDefault
File size warningfile_size_warn500 lines
File size errorfile_size_error1000 lines
Coverage failurecoverage_threshold80%
Coverage warningcoverage_warn_threshold60%
Major version lagdeps_max_major_behind1
Minor version lagdeps_max_minor_behind3

3. Analysis Commands Are Read-Only

<rules> Analysis commands (dead_code, circular_imports, unused_deps, dep_graph) report findings but never modify code. They return structured data for agents to act on — the agent decides what to fix. </rules>

Command Overview

Core Commands (Language-Dispatched)

CommandPythonTypeScriptRust
dev_lint()ruff checkbiome lintcargo clippy
dev_test()pytestvitest runcargo test
dev_build()hatch buildturbo buildcargo build
dev_skill_lint()(universal)(universal)(universal)

Quality Commands

CommandWhat It Checks
dev_check_size()Python file line counts vs thresholds
dev_check_coverage()Test coverage vs threshold (runs pytest --cov)
dev_check_deps()Dependency versions vs PyPI latest

Analysis Commands

CommandWhat It Finds
dev_dead_code()Unused functions, variables, imports (via vulture)
dev_circular_imports()Import cycles using AST + DFS
dev_unused_deps()Declared but not imported dependencies
dev_dep_graph()Module dependency graph (JSON or DOT)

Portability Commands

CommandWhat It Detects
dev_check_paths()Hardcoded Windows/Unix paths, localhost URLs

Workflow

Daily Development Flow

  1. Write code — make changes
  2. Lintdev_lint() catches style and syntax issues
  3. Testdev_test() runs the test suite
  4. Quality gatesdev_check_size(), dev_check_coverage() validate standards

Pre-Release Analysis

  1. Dead codedev_dead_code() finds unused symbols
  2. Circular importsdev_circular_imports() detects cycles
  3. Unused depsdev_unused_deps() finds removable dependencies
  4. Dep freshnessdev_check_deps() checks for staleness
  5. Portabilitydev_check_paths() ensures cross-platform compatibility

Checklist

  • dev_lint() passes with no errors
  • dev_test() passes with no failures
  • dev_check_size() — no files exceed error threshold
  • dev_check_coverage() — meets coverage threshold
  • dev_check_deps() — no major-version-behind dependencies
  • dev_circular_imports() — within allowed cycle count
  • dev_check_paths() — no hardcoded platform-specific paths

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is run-dev-checks?

Perfect for Code Review Agents needing advanced language-aware linting and testing capabilities for Python, TypeScript, and Rust run-dev-checks is a skill that automates code quality checks, providing language-aware linting, testing, and building capabilities for developers.

How do I install run-dev-checks?

Run the command: npx killer-skills add lushly-dev/afd/run-dev-checks. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for run-dev-checks?

Key use cases include: Automating code quality checks for Python, TypeScript, and Rust projects, Validating test coverage and dependency freshness against customizable thresholds, Analyzing code structure to identify dead code and circular imports.

Which IDEs are compatible with run-dev-checks?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for run-dev-checks?

Supports only Python, TypeScript, and Rust languages. Requires configuration of thresholds for code quality checks.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add lushly-dev/afd/run-dev-checks. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use run-dev-checks immediately in the current project.

Related Skills

Looking for an alternative to run-dev-checks or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

openclaw-release-maintainer is a specialized AI agent skill for automating release management workflows.

333.8k
0
Data

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
Design

flags

Logo of vercel
vercel

flags is a skill for managing feature flags in Next.js internals, enabling developers to efficiently configure and optimize their React applications.

138.4k
0
Browser

x-api

[ Featured ]
Logo of affaan-m
affaan-m

x-api is a skill that harnesses performance optimization for AI agents, enabling efficient interactions with Twitter and other platforms.

103.8k
0
Productivity