You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(framework): replace hardcoded npx with a <runner> placeholder in skills #1044
Summary: Several shipped skills hardcode npx in their commands; users on alternative Node runners (pnpx, bunx, nubx, pnpm dlx, …) cannot run them.
🌟 Objective / Problem
Skills under plugins/ invoke npx directly. On machines where npx is not installed — increasingly common with alternative Node toolchains — the affected skills fail. Example: 01-acceptance-qa requires resolving npx as a prerequisite, so the whole QA flow is blocked on such machines.
Affected locations (found by grepping the shipped plugins for npx):
Replace every hardcoded npx in skill content with a <runner> placeholder, meaning "any package runner: npx, pnpx, bunx, nubx, pnpm dlx, …".
State the convention once at the top of each affected file, e.g.: <runner> is your package runner: npx, pnpx, bunx, nubx, …
In the 01-acceptance-qa prerequisites check, resolve whichever runner is available instead of requiring npx specifically.
🔍 Context / Technical Constraints (Optional)
Out of scope: historical records under aidd_docs/tasks/ and the CLI install docs (cli/README.md), where npx @ai-driven-dev/cli@latest setup is the canonical npm install path.
🙏 QA
Validation must be done with an alternative package runner (pnpx, bunx, nubx, pnpm dlx, …) — not with npm/npx.
No hardcoded npx remains in the shipped skills under plugins/
Each file that uses <runner> defines the placeholder once
01-acceptance-qa prerequisites pass on a machine where npx is absent, resolving an alternative runner instead
The 01-acceptance-qa flow runs end to end through an alternative runner (pnpx, bunx or nubx) and produces its evidence videos
Activity