skills.rest
pikakit
pikakitCOMMUNITY
Explore all skills by this author →
𝕏@realpikakitGitHub

problem-checker

Detect and fix IDE problems in TypeScript/JavaScript and CSS edits.

Updated Jan 24, 2026
Search Tags:#automation#typescript#javascript#css#auto-fix#pre-commit#ide-errors
One-click install
npx skills add https://github.com/pikakit/agent-skills --skill problem-checker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: problem-checker
Source: https://github.com/pikakit/agent-skills/tree/main/.agent/skills/problem-checker
Command: npx skills add https://github.com/pikakit/agent-skills --skill problem-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

IDE-driven quality gates require proactive checks before task completion. The Problem Checker reads current IDE problems, classifies them into auto-fixable issues and escalations, and applies deterministic fixes to common patterns to keep your codebase clean without interrupting workflow.

Core Features & Use Cases

  • Automatically detects and fixes four patterns: Missing import, JSX namespace, Unused variable, and CSS @import order.
  • Verifies results in cycles (max 3 by default) and hard-blocks on unresolved errors to prevent broken tasks.
  • Provides structured output and escalation paths when issues remain after fixes.

Quick Start

Run the Problem Checker against your codebase to automatically detect IDE problems, apply known fixes, and verify results.

Frequently Asked Questions about problem-checker

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

FAQPage Schema
How do I automatically fix TypeScript and CSS IDE errors before commit?▼

Automatically fixing TypeScript and CSS IDE errors before commit requires reading current IDE problems, classifying them, and applying deterministic auto-fixes. The Skill targets four specific patterns: missing imports, JSX namespaces, unused variables, and CSS @import order.

What is a pre-commit hard-block policy for IDE problems?▼

A pre-commit hard-block policy for IDE problems stops task completion when unresolved errors remain after applying auto-fixes. It enforces a max 3-cycle verification loop to ensure codebase quality and prevents broken tasks from proceeding.

How do I resolve missing import and JSX namespace issues in JavaScript?▼

Resolving missing import and JSX namespace issues in JavaScript involves applying deterministic auto-fix patterns. The checker identifies these specific IDE problems and automatically applies the correct imports or namespace declarations to keep code clean.

Does the auto-fix checker support frameworks beyond TypeScript and CSS?▼

The auto-fix checker operates specifically across TypeScript, JavaScript, and CSS edits. It applies a fixed set of four auto-fix patterns and does not support other languages or frameworks outside of this scope.

What happens when auto-fix fails to resolve TypeScript errors after 3 cycles?▼

When auto-fix fails to resolve TypeScript errors after 3 cycles, the system triggers a hard-block policy and provides structured escalation paths. It stops the current task and escalates the remaining unresolved issues rather than proceeding.

Related Skills

Explore More Software Engineering Skills→
jmaglyjmagly
175

eslint-checker

Execute ESLint to enforce code quality and style for JavaScript and TypeScript projects.

Community
Intermediate
nq-rdlnq-rdl

pre-commit

Manage multi-language pre-commit hooks from .pre-commit-config.yaml using pixi.

Official
Intermediate
xotongxotong

lint-and-validate

Run linters, formatters, and type checkers on code changes before commits.

Community
Intermediate
MBarry01MBarry01

iterative-retrieval

Narrow relevant information from large codebases through a deterministic 4-phase retrieval loop.

Community
Advanced