All Skills Search Tools

|

Loading...

AI Agent Skills Directory with categorization, English/Chinese translation, and script security checks.

Sitemap

Home
All Skills
Search
Tools

About

About Us
Disclaimer
Copyright

Help

FAQ
Privacy
Terms

Contact Us:osulivan147@qq.com

© 2026 Skill4Agent. All rights reserved.

Home/All Skills/Code Quality/check-compiler-errors

check-compiler-errors

Original：🇺🇸 English

Translated

Run compile and type-check commands and report failures

9installs

Sourcecursor/plugins

Added on2026-05-23

NPX Install

npx skill4agent add cursor/plugins check-compiler-errors

Tags

Translated version includes tags in frontmatter

code-compilation type-checking error-reporting ci-validation code-fixing

SKILL.md Content

View Translation Comparison →

Check compiler errors

Trigger

Compile or type-check failures are blocking local validation or CI.

Workflow

Run the repo's compile and type-check commands.
Summarize errors by file and type.
Fix the highest-confidence issues first.
Re-run checks until clean or blocked.

Output

Current compile and type-check status
Error summary grouped by file and category
Fixes applied and remaining blockers

Download

Download TranslatedIncludes original Skill.md

(1.0 KB)Download Original(452 B)

Related Skills

naming-analyzer

Suggest better variable, function, and class names based on context and conventions.

ponytail

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.

setup-pre-commit

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

improve-codebase-architecture

Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.