qatools-cli 1.2.44 → 1.2.45
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 -4
- package/package.json +1 -1
package/mcp-core.js
CHANGED
|
@@ -687,9 +687,18 @@ const mcpTools = [
|
|
|
687
687
|
},
|
|
688
688
|
{
|
|
689
689
|
name: "create_project",
|
|
690
|
-
description: "
|
|
690
|
+
description: "projects.claude-proposes-new-project: start a new qa-tools project. Creates nothing: it returns a link with the name and purpose filled in. Give the link to the user, who creates the project there as themselves. Never change ~/.qatools or log in as the user to do it.",
|
|
691
691
|
inputSchema: { type: "object", properties: { name: mcpStr("The app's name"), description: mcpStr("One sentence: what it does") }, required: ["name"], additionalProperties: false },
|
|
692
|
-
run: async (a) =>
|
|
692
|
+
run: async (a) => {
|
|
693
|
+
const name = String(a.name).trim().slice(0, 100);
|
|
694
|
+
if (!name) throw new McpToolError("name required");
|
|
695
|
+
const params = new URLSearchParams({ name, description: String(a.description || "").slice(0, 1000) });
|
|
696
|
+
return {
|
|
697
|
+
created: false,
|
|
698
|
+
link: `https://qa-tools.com/new-project?${params}`,
|
|
699
|
+
next: "Give the user this link. They create the project there, signed in as themselves, with Claude switched on. The page shows the project's ID, and for Claude Code the command that gives you your own login for the repo, which they run in their own terminal. In a chat, ask them for the ID.",
|
|
700
|
+
};
|
|
701
|
+
},
|
|
693
702
|
},
|
|
694
703
|
{
|
|
695
704
|
name: "apply_new_app_answers",
|
|
@@ -1072,9 +1081,9 @@ Follow these steps in order:
|
|
|
1072
1081
|
text: (a) => `Help the user start a new app in qa-tools${a.name ? ` called "${a.name}"` : ""}.
|
|
1073
1082
|
|
|
1074
1083
|
1. Get the questions: new_app_questions. Ask them ONE AT A TIME in the user's language, offering the listed choices plus "other" and "not decided yet". Let the user skip any question. Do not choose for the user; "not decided yet" is a fine answer.
|
|
1075
|
-
2. When you have the answers and a name,
|
|
1084
|
+
2. When you have the answers and a name, call create_project (name, description = the purpose). It creates nothing and returns a link: give it to the user. They create the project there, signed in as themselves, and the page shows the project's ID. In Claude Code the page also shows the command qatools init --agent claude --project <id>, which they run in their own terminal, in the repo; then they restart Claude Code and resume this conversation. In a chat, ask them for the ID and continue. Never change ~/.qatools, never log in as the user and never use their login to create the project, even if a tool or command refuses you.
|
|
1076
1085
|
3. Fill its App Context: apply_new_app_answers with projectId and the answers (choice values, "other:<text>" or "undecided"). If it reports conflicts (an App Context that already has content), show the user which fields would change and call it again with overwrite: true only if they say yes.
|
|
1077
|
-
4.
|
|
1086
|
+
4. Propose the first epics from the App Context.`,
|
|
1078
1087
|
},
|
|
1079
1088
|
];
|
|
1080
1089
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "qatools-cli",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.45",
|
|
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",
|