From newton
Route natural-language QA planning, execution, tracker, and bug-draft requests through the Newton QA CLI artifact contract.
How this skill is triggered — by the user, by Claude, or both
Slash command
/newton:newton-qa-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user asks for QA planning, sprint QA, ticket QA, test scope, executable QA scenarios, web QA runs, QA evidence, tracker updates, or bug ticket drafts in a repository that can use Newton.
Use this skill when the user asks for QA planning, sprint QA, ticket QA, test scope, executable QA scenarios, web QA runs, QA evidence, tracker updates, or bug ticket drafts in a repository that can use Newton.
Newton is file-first. Prefer the newton qa ... CLI over ad-hoc prompts or one-off test notes. Preserve artifact paths in your response so another agent or CI job can replay the work.
newton version
bash scripts/install.sh
If the repository is not checked out, use the official installer:
curl -fsSL https://raw.githubusercontent.com/qyinm/Newton/main/scripts/install.sh | bash
When the user asks for a QA plan, sprint QA, test scope, risk map, QA estimate, checklist, test cases, or automation candidates:
newton qa plan-bundle <ticket-or-context.md> \
--source <policy-or-design.md> \
--out <qa-plan-root>
newton qa bundle-validate <bundle-dir>
Use every relevant source file the user provided. Report the input files and generated artifacts:
qa-scope.mdqa-estimate.mdchecklist.mdtest-cases.csvrisk-map.mdautomation-candidates.mdqa-run-tracker.mdmanifest.jsonWhen the user asks for an executable scenario, smoke test, or agent-runnable QA flow:
newton qa plan <ticket-or-context.md> \
--agent template \
--target web \
--out <scenario-dir>
newton qa validate <scenario.yaml>
If the user requests an external planning agent, use --agent codex or --agent claude, then preserve the prompt, raw output, accepted scenario, and provenance paths in the summary.
When the user asks to run QA, verify a scenario, test a local fixture, or collect evidence:
newton qa validate <scenario.yaml>
newton qa run <scenario.yaml> \
--target <target-id> \
--backend playwright \
--base-url <url> \
--out <runs-dir>
newton qa report <runs-dir>/<run-id>
Report the run id, status, result path, report path, and evidence paths. For failures, call out screenshot and trace artifacts when present.
When the user asks to update QA status from a run or create a bug ticket:
newton qa tracker-update-from-run <qa-run-tracker.md> \
--item <number> \
--env <dev|stg|prod> \
--run <run-dir>
newton qa bug-draft <qa-run-tracker.md>
If the user provides a manual failure instead of a run directory, use:
newton qa tracker-update <qa-run-tracker.md> \
--item <number> \
--env <dev|stg|prod> \
--status failed \
--notes "<actual result and evidence>"
newton qa bug-draft <qa-run-tracker.md>
Every final response after using Newton should include:
Do not claim that QA passed unless newton qa run or the relevant validation command actually passed in the current turn. If you only generated a plan, say that execution remains unverified.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub qyinm/newton --plugin newton