How do I install the Local QA skill?

Run npx skillmds@latest add dceoy/local-qa in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Local QA skill do?

Run local QA including formatting, linting, type-checking, static site build, and workflow checks for the repository. Use whenever any file has been updated. It is listed under Productivity, Coding & Dev Tools on SkillMD.

Is Local QA safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Local QA?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Local QA free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Local QA?

dceoy (@dceoy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Local QA by dceoy — Agent Skill

Name: Local QA
Rating: 4.2 (5 reviews)
Author: dceoy

File contents

Local QA (format, lint, type-check, and build)

Run the local QA script for this repository:

.agents/skills/local-qa/scripts/qa.sh

Procedure

Execute the script exactly as shown above when this skill is triggered.
Capture and summarize key output: success/failure, major warnings, and any files modified.
If the script fails due to missing tooling (command not found, missing executable, or equivalent), install the missing tool(s) and rerun .agents/skills/local-qa/scripts/qa.sh.
Install tools using this order of preference:
1. Use the project's package manager when applicable (uv for Python, package manager scripts/dependencies for Node.js).
2. Use a system package manager (brew on macOS, apt on Debian/Ubuntu) when project-local install is not applicable.
3. Use language-specific installers as fallback (pipx/pip, npm, go install, etc.).
If multiple tools are missing, repeat install -> rerun until QA completes or you hit a blocker.
If installation fails or requires unavailable privileges, report what was attempted, the exact failure, and stop.
Do not run unrelated commands; only run commands needed for QA and missing-tool installation.

Frequently asked questions

Local QA