Automated Task Validator FAQs

Question 1

Does jp-task-validate automatically fix my code errors?

Accepted Answer

No, this skill is strictly for reporting. It detects and identifies issues like syntax errors or failing tests but does not modify your files, leaving the fixing process to the developer or a separate code-repair agent.

Question 2

Can it run tests for both Python and Node.js projects?

Accepted Answer

Yes, it supports Pytest for Python projects and standard npm/yarn/pnpm test scripts for Node.js environments, including support for frameworks like Jest and Vitest.

Question 3

Does it require a specific project layout to work?

Accepted Answer

While it works best with standard layouts, it is highly adaptable. It scans for configuration files like package.json or pyproject.toml to determine the best validation strategy for your specific environment.

Question 4

How does the skill determine if a file is in the wrong place?

Accepted Answer

It performs a file structure verification by comparing the paths of modified files against standard project conventions (e.g., source code in src/, tests in tests/) and issues warnings for non-standard placements.

Question 5

What happens if my project uses a linter not listed in the documentation?

Accepted Answer

The skill checks your project configuration and PATH for supported tools. If a tool isn't detected, it will either fall back to basic syntax checks (like using the Python AST) or skip that specific check silently.

Automated Task Validator

主な機能

ユースケース

Automated Task Validator

主な機能

ユースケース