qatools-cli 1.2.37 → 1.2.39
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/mcp-core.js +13 -3
- package/package.json +1 -1
package/mcp-core.js
CHANGED
|
@@ -79,7 +79,7 @@ function loopRunPrompt(projectId) {
|
|
|
79
79
|
return `You are running UNATTENDED in this app's git repository, as the developer of the qa-tools project${projectId ? ` ${projectId}` : ""}. Nobody is at the keyboard. The people who made the wishes work only in qa-tools: everything you say to them goes into the wish (the backlog item) as a comment, in their language, in plain words — no code, file names or technical terms.
|
|
80
80
|
|
|
81
81
|
Hard rules — never break them:
|
|
82
|
-
- Use this repo's qa-tools key (QATOOLS_API_KEY, or the key file the repo documents) and pass the project; never run qatools setup or qatools login — they change the computer-wide default that other projects use. If an MCP tool refuses with "API key is not valid for this project", the MCP server runs on another project's login: do the same through the CLI with this repo's key (QATOOLS_API_KEY=<key> qatools …), e.g. qatools notify instead of notify_owner.
|
|
82
|
+
- Use this repo's qa-tools key (QATOOLS_API_KEY, or the key file the repo documents) and pass the project; never run qatools setup or qatools login — they change the computer-wide default that other projects use. If an MCP tool refuses with "API key is not valid for this project", the MCP server runs on another project's login: do the same through the CLI with this repo's key (QATOOLS_API_KEY=<key> qatools …), e.g. qatools notify instead of notify_owner or notify_member.
|
|
83
83
|
- Never deploy to production, never merge into the main branch, never push to it. Production is a person's decision.
|
|
84
84
|
- Never approve a requirement, and never set a wish to resolved. You draft; a person approves and confirms.
|
|
85
85
|
- At most ONE wish is built per run. When a test keeps failing or something is unclear, stop and say so in the wish.
|
|
@@ -90,13 +90,13 @@ Steps, in order:
|
|
|
90
90
|
1. Wishes to answer: list_backlog (statuses open, in_progress). A wish is an item written by a person (not by Claude). Read its comments. Answer when it has no comment from you yet, or when the person wrote after your last comment:
|
|
91
91
|
- Something important unclear: ask ONE concrete question with 2–4 short choices (update_backlog_item comment).
|
|
92
92
|
- Clear: write "Så här har jag förstått dig:" / "This is how I understood you:" and in a few plain sentences what will be built, ending with "Svara ja om det stämmer, annars vad som ska ändras." / "Answer yes if that is right, otherwise what to change."
|
|
93
|
-
- When you write your understanding, also write the requirement as a DRAFT (create_requirement status draft, Given/When/Then in the wish's language, never mixing languages) and link the wish to it (update_backlog_item requirementKey). The person approves it in the wish with "Ja, det stämmer" / "Yes, that is right" — that sets the requirement approved. Never approve it yourself, and do not build it before it is approved. Tell the person who made the wish ONCE that it waits for their yes (qatools notify --to <them
|
|
93
|
+
- When you write your understanding, also write the requirement as a DRAFT (create_requirement status draft, Given/When/Then in the wish's language, never mixing languages) and link the wish to it (update_backlog_item requirementKey). The person approves it in the wish with "Ja, det stämmer" / "Yes, that is right" — that sets the requirement approved. Never approve it yourself, and do not build it before it is approved. Tell the person who made the wish ONCE that it waits for their yes (notify_member, or qatools notify --to <them>; plain words, the wish's label; it respects their opt-out) — not again on later runs.
|
|
94
94
|
At most 6 answers from you per wish; after that, say a person needs to look at it.
|
|
95
95
|
|
|
96
96
|
2. Build one approved wish: list_requirements status approved; take the first that a wish links to (its requirementKey) and that is not started. Then:
|
|
97
97
|
- update_requirement status in_progress, assignedTo "me"; comment in the wish that you have started.
|
|
98
98
|
- git switch -c loop/<requirement key> from the main branch (git pull first). Implement it the way the repo already works (read CLAUDE.md and the code around it). Add or extend automated tests for its acceptance criteria.
|
|
99
|
-
- Run the repo's tests and build. If they fail and you cannot fix it: commit the work in progress on the branch, push the branch, set the requirement back to approved, and comment in the wish what stops you, in plain words. Stop.
|
|
99
|
+
- Run the repo's tests and build in a mode that ends by itself (no watch mode: e.g. --watch=false, CI=true; tests in a subfolder with npm test --prefix <folder>). If they fail and you cannot fix it: commit the work in progress on the branch, push the branch, set the requirement back to approved, and comment in the wish what stops you, in plain words. Stop.
|
|
100
100
|
- When everything passes: commit (the message names the requirement key), push the branch, open a pull request if gh is available.
|
|
101
101
|
- Test environment: get_app_context. If its environments list one named test (or Test, staging), deploy the branch there with the repo's own documented test deploy, and check that the change works there. If there is none, do NOT deploy.
|
|
102
102
|
- update_requirement status implemented with evidence: the test output (numbers), the branch and commit, and the test address if deployed.
|
|
@@ -496,6 +496,16 @@ const mcpTools = [
|
|
|
496
496
|
}, ["requirementKey", "result", "evidence"]),
|
|
497
497
|
run: async (a) => mcpCall("recordSprintVerification", { projectId: a.projectId, ...mcpPick(a, ["requirementKey", "result", "evidence", "sprintId", "commit"]), attachments: await uploadEvidenceFiles(a.projectId, a.attachments) }),
|
|
498
498
|
},
|
|
499
|
+
{
|
|
500
|
+
name: "notify_member",
|
|
501
|
+
description: "Email one project member, e.g. the person who made a wish that now waits for their yes (respects their opt-out — a mail they turned off is not sent). An addressed, deliberate message; plain text.",
|
|
502
|
+
inputSchema: mcpSchema({
|
|
503
|
+
to: mcpStr("The member's email"),
|
|
504
|
+
subject: mcpStr("Email subject"),
|
|
505
|
+
message: mcpStr("Plain-text body"),
|
|
506
|
+
}, ["to", "subject", "message"]),
|
|
507
|
+
run: async (a) => mcpCall("notifyUser", { projectId: a.projectId, to: a.to, subject: a.subject, message: a.message }),
|
|
508
|
+
},
|
|
499
509
|
{
|
|
500
510
|
name: "notify_owner",
|
|
501
511
|
description: "Email the project owner (respects their opt-out). Used for the summary at the end of a scheduled agenda run. Plain text.",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "qatools-cli",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.39",
|
|
4
4
|
"description": "CLI for QA Tools — requirements, epics, sprints, sessions, App Context sync, project agenda. The companion to qa-tools.com.",
|
|
5
5
|
"scripts": {
|
|
6
6
|
"release": "npm version patch --no-git-tag-version && npm publish",
|