fix(framework): replace hardcoded npx with a <runner> placeholder in skills
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 78/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- node.js, playwright, typescript
调研方向
Start with the three listed files: the Playwright CLI reference, the acceptance QA prerequisites, and the MCP installation recipe. Find each npx use, add the runner convention in each file, and update prerequisite detection to accept an available alternative runner. Validate using an alternative runner; done means no hardcoded npx remains in shipped skills and the QA flow produces its evidence videos.
由索引模型根据 Issue 内容生成。
描述
Summary: Several shipped skills hardcode
npxin 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):
plugins/aidd-qa/skills/01-acceptance-qa/references/interface-browser-playwright-cli.md— 6 occurrences, e.g.npx --yes @playwright/[email protected] -s=qa-<run-id> <command>plugins/aidd-qa/skills/01-acceptance-qa/actions/02-prerequisites.md— 2 occurrences (the check resolvesnpxand runsnpx --yes @playwright/[email protected] --version)plugins/aidd-context/skills/12-cook/assets/recipes/mcp-installation.md— 1 occurrence (npx playwright)
🛠️ Proposed Solution
- Replace every hardcoded
npxin 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-qaprerequisites check, resolve whichever runner is available instead of requiringnpxspecifically.
🔍 Context / Technical Constraints (Optional)
- Out of scope: historical records under
aidd_docs/tasks/and the CLI install docs (cli/README.md), wherenpx @ai-driven-dev/cli@latest setupis 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
npxremains in the shipped skills underplugins/ - Each file that uses
<runner>defines the placeholder once -
01-acceptance-qaprerequisites pass on a machine wherenpxis absent, resolving an alternative runner instead - The
01-acceptance-qaflow runs end to end through an alternative runner (pnpx,bunxornubx) and produces its evidence videos
- 主要语言
- TypeScript
- 星标
- 481
- 派生
- 45
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 77
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ai-driven-dev/framework 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
ai-driven-dev/framework#1050 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
ai-driven-dev/framework#1035 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
ai-driven-dev/framework#1002 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
ai-driven-dev/framework#952 ·
维护者通常 1 天内回复
-
refactor(aidd-orchestrator): the check zone says when to stop, and reviews its axes in one round未关闭
难度 2/5 1-3 小时 新手友好度 76/100
ai-driven-dev/framework#887 ·
维护者通常 1 天内回复
查看 ai-driven-dev/framework 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
simkimsia/netlify-axi#19 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
subhranshudash13-dotcom/Contribo#74 ·
维护者通常 1 天内回复
-
enhancement frontend good first issue Stellar Wave trivial
难度 2/5 1-3 小时 新手友好度 76/100
Godgift-care/sci-healthcare-frontend#166 · 1 条评论 ·
维护者通常 1 天内回复
-
backend good first issue security Stellar Wave trivial
难度 2/5 1-3 小时 新手友好度 82/100
Godgift-care/sci-healthcare-backend#171 · 1 条评论 ·
维护者通常 1 天内回复