jp-task-validate

Automate post-task validation by invoking the skill with specific file paths to detect syntax errors, type issues, failing tests, and broken imports. It scopes checks to modified files and generates a consolidated report without attempting fixes.

Yes, the validation tool detects existing project tooling including pytest, flake8, ruff, eslint, biome, mypy, and tsc. It automatically runs the appropriate checks based on the detected tools and reports structured findings.

Run linting and import checks by invoking the skill with the affected file paths. It inventories the input files, verifies their existence, and performs syntax validation and linting across Python, JavaScript, TypeScript, JSON, YAML, Markdown, and shell scripts.

Yes, you can validate broken imports and misplaced files without fixes. The skill performs basic import resolution checks, detects misplaced files in updated project artifacts, and reports all findings in a structured format without attempting any code modifications.

Project tooling must be present or detectable because the skill relies on existing frameworks like pytest, mypy, and eslint to execute checks. Without these tools installed, the skill cannot run the appropriate syntax, type, and test validations.

You should not use automated post-task checks when you need a tool to fix detected issues, as this skill only reports findings. Additionally, if your project lacks detectable tooling like pytest, flake8, or eslint, the appropriate checks cannot be executed.