dceoy/mt5api · Archived

local-qa

Run local QA including formatting, linting, and testing for the repository. Use whenever any file has been updated.

Installation

$ npx skills add dceoy/mt5api --skill local-qa

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dceoy/mt5api.

npx skills add dceoy/mt5api

Browse all from dceoy/mt5api

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,326 B
  • docs SUMMARY.md 131 B

History

  1. First recorded snapshot · 1 installs

SKILL.md

Local QA (format, lint, and test)

Run the local QA script scripts/qa.sh in this skill.

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 ./scripts/qa.sh.
  • Install tools using this order of preference:

1. Use the project's package manager when applicable (uv/poetry 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.