@bugzy-ai/bugzy 1.2.1 → 1.4.0

package/dist/index.cjs

@@ -60,6 +60,7 @@ var MCP_SERVERS = {
     name: "Slack",
     description: "Slack MCP server for messaging and channel operations",
     requiresCredentials: true,
+    npmPackages: ["simple-slack-mcp-server"],
     config: {
       command: "slack-mcp-server",
       args: [],
@@ -73,6 +74,7 @@ var MCP_SERVERS = {
     name: "Microsoft Teams",
     description: "Microsoft Teams MCP server for messaging and channel operations",
     requiresCredentials: true,
+    npmPackages: ["@bugzy-ai/teams-mcp-server"],
     config: {
       command: "teams-mcp-server",
       args: [],
@@ -86,6 +88,7 @@ var MCP_SERVERS = {
     name: "Playwright",
     description: "Playwright MCP server for browser automation",
     requiresCredentials: false,
+    npmPackages: ["@playwright/mcp"],
     config: {
       command: "mcp-server-playwright",
       args: [
@@ -110,6 +113,7 @@ var MCP_SERVERS = {
     name: "Notion",
     description: "Notion MCP server for documentation",
     requiresCredentials: true,
+    npmPackages: ["@notionhq/notion-mcp-server"],
     config: {
       command: "notion-mcp-server",
       args: [],
@@ -123,6 +127,7 @@ var MCP_SERVERS = {
     name: "Jira Server (On-Prem)",
     description: "Jira Server MCP via tunnel for on-premise instances",
     requiresCredentials: true,
+    npmPackages: ["@mcp-tunnel/wrapper", "@bugzy-ai/jira-mcp-server"],
     config: {
       command: "mcp-tunnel",
       args: ["--server", "jira-mcp-server"],
@@ -708,7 +713,9 @@ Document all findings including:
 \`\`\`
 
 #### 3.2 Launch Test Runner Agent
-Invoke the test-runner agent with special exploration instructions:
+{{INVOKE_TEST_RUNNER}}
+
+Execute the exploration test case with special exploration instructions:
 
 \`\`\`
 Execute the exploration test case at ./test-cases/EXPLORATION-TEMP.md with focus on discovery and documentation.
@@ -1161,10 +1168,10 @@ Before invoking the agent, identify the test cases for the current area:
 
 #### Step 2.2: Invoke test-code-generator Agent
 
-Use the test-code-generator agent for the current area with the following context:
+{{INVOKE_TEST_CODE_GENERATOR}} for the current area with the following context:
 
 **Agent Invocation:**
-"Use the test-code-generator agent to automate test cases for the [AREA_NAME] area.
+"Automate test cases for the [AREA_NAME] area.
 
 **Context:**
 - Area: [AREA_NAME]
@@ -1304,10 +1311,10 @@ Provide a comprehensive summary showing:
       role: "documentation-researcher",
       contentBlock: `#### 1.4 Gather Product Documentation
 
-Use the documentation-researcher agent to gather comprehensive product documentation:
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to gather comprehensive product documentation:
 
 \`\`\`
-Use the documentation-researcher agent to explore all available product documentation, specifically focusing on:
+Explore all available product documentation, specifically focusing on:
 - UI elements and workflows
 - User interactions and navigation paths
 - Form fields and validation rules
@@ -1321,10 +1328,9 @@ Use the documentation-researcher agent to explore all available product document
       role: "team-communicator",
       contentBlock: `### Step 4.5: Team Communication
 
-Use the team-communicator agent to notify the product team about the new test cases and automated tests:
+{{INVOKE_TEAM_COMMUNICATOR}} to notify the product team about the new test cases and automated tests:
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post an update about test case and automation creation
 2. Provide summary of coverage:
    - Number of manual test cases created
@@ -1582,10 +1588,10 @@ Provide a summary of:
       role: "documentation-researcher",
       contentBlock: `### Step 2: Gather comprehensive project documentation
 
-Use the documentation-researcher agent to explore and gather all available project information and other documentation sources. This ensures the test plan is based on complete and current information.
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to explore and gather all available project information and other documentation sources. This ensures the test plan is based on complete and current information.
 
 \`\`\`
-Use the documentation-researcher agent to explore all available project documentation related to: $ARGUMENTS
+Explore all available project documentation related to: $ARGUMENTS
 
 Specifically gather:
 - Product specifications and requirements
@@ -1610,10 +1616,9 @@ The agent will:
       role: "team-communicator",
       contentBlock: `### Step 7.5: Team Communication
 
-Use the team-communicator agent to notify the product team about the new test plan:
+{{INVOKE_TEAM_COMMUNICATOR}} to notify the product team about the new test plan:
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post an update about the test plan creation
 2. Provide a brief summary of coverage areas and key features
 3. Mention any areas that need exploration or clarification
@@ -1848,7 +1853,7 @@ Classify the ambiguity level to determine appropriate response:
 #### Clarification Approach by Severity
 
 **For CRITICAL/HIGH ambiguity:**
-1. **Use team-communicator to ask specific questions**
+1. **{{INVOKE_TEAM_COMMUNICATOR}} to ask specific questions**
 2. **WAIT for response before proceeding**
 3. **Document the clarification request in event history**
 
@@ -2121,7 +2126,7 @@ ${KNOWLEDGE_BASE_UPDATE_INSTRUCTIONS}`,
       contentBlock: `#### 3.3 Use Documentation Researcher if Needed
 For events mentioning unknown features or components:
 \`\`\`
-Use documentation-researcher agent to find information about: [component/feature]
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to find information about: [component/feature]
 \`\`\``
     },
     {
@@ -2130,7 +2135,7 @@ Use documentation-researcher agent to find information about: [component/feature
 
 When an issue needs to be tracked (task type: report_bug or update_story):
 \`\`\`
-Use issue-tracker agent to:
+{{INVOKE_ISSUE_TRACKER}}
 1. Check for duplicate issues in the tracking system
 2. For bugs: Create detailed bug report with:
    - Clear, descriptive title
@@ -2399,7 +2404,7 @@ For each failed test:
 For each test classified as **[TEST ISSUE]**, use the test-debugger-fixer agent to automatically fix the test:
 
 \`\`\`
-Use the test-debugger-fixer agent to fix test issues:
+{{INVOKE_TEST_DEBUGGER_FIXER}}
 
 For each failed test classified as a test issue (not a product bug), provide:
 - Test run timestamp: [from manifest.timestamp]
@@ -2494,7 +2499,7 @@ After triage in Step 5.1, for tests classified as **[PRODUCT BUG]**, use the iss
 For each bug to report, use the issue-tracker agent:
 
 \`\`\`
-Use issue-tracker agent to:
+{{INVOKE_ISSUE_TRACKER}}
 1. Check for duplicate bugs in the tracking system
    - The agent will automatically search for similar existing issues
    - It maintains memory of recently reported issues
@@ -2565,10 +2570,11 @@ After issue tracker agent completes, create a summary:
       role: "team-communicator",
       contentBlock: `### Step 6: Team Communication
 
-Use the team-communicator agent to notify the product team about test execution:
+{{INVOKE_TEAM_COMMUNICATOR}}
+
+Notify the product team about test execution:
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post test execution summary with key statistics
 2. Highlight critical failures that need immediate attention
 3. Share important learnings about product behavior
@@ -2903,7 +2909,7 @@ Read and analyze the JSON report:
 For each test classified as **[TEST ISSUE]**, use the test-debugger-fixer agent to automatically fix the test:
 
 \`\`\`
-Use the test-debugger-fixer agent to fix test issues:
+{{INVOKE_TEST_DEBUGGER_FIXER}}
 
 For each failed test classified as a test issue (not a product bug), provide:
 - Test file path: [from JSON report]
@@ -2944,7 +2950,7 @@ Classification guidelines:
 #### 4A.4 Fix Test Issues Automatically
 
 For tests classified as [TEST ISSUE]:
-- Use test-debugger-fixer agent to analyze and fix
+- {{INVOKE_TEST_DEBUGGER_FIXER}} to analyze and fix
 - Agent debugs with browser if needed
 - Applies fix (selector update, wait condition, assertion correction)
 - Reruns test to verify fix (10x for flaky tests)
@@ -2960,7 +2966,7 @@ Track fixed tests with:
 {{ISSUE_TRACKER_INSTRUCTIONS}}
 
 For tests classified as [PRODUCT BUG]:
-- Use issue-tracker agent to create bug reports
+- {{INVOKE_ISSUE_TRACKER}} to create bug reports
 - Agent checks for duplicates automatically
 - Creates detailed report with:
   - Title, description, reproduction steps
@@ -3276,10 +3282,10 @@ Format as comprehensive markdown report for terminal display:
 
 {{TEAM_COMMUNICATOR_INSTRUCTIONS}}
 
-Use team-communicator agent to post concise results to Slack thread:
+{{INVOKE_TEAM_COMMUNICATOR}} to post concise results to Slack thread:
 
 \`\`\`
-Use the team-communicator agent to post verification results.
+Post verification results.
 
 **Channel**: [from CHANGE_CONTEXT.slackChannel]
 **Thread**: [from CHANGE_CONTEXT.slackThread]
@@ -3460,10 +3466,10 @@ A successful verification includes:
       role: "documentation-researcher",
       contentBlock: `#### Research Project Documentation
 
-Use the documentation-researcher agent to gather comprehensive context about the changed features:
+{{INVOKE_DOCUMENTATION_RESEARCHER}} to gather comprehensive context about the changed features:
 
 \`\`\`
-Use the documentation-researcher agent to explore project documentation related to the changes.
+Explore project documentation related to the changes.
 
 Specifically gather:
 - Product specifications for affected features
@@ -3495,10 +3501,9 @@ Use this information to:
       role: "issue-tracker",
       contentBlock: `#### Log Product Bugs
 
-For tests classified as **[PRODUCT BUG]**, use the issue-tracker agent to log bugs:
+For tests classified as **[PRODUCT BUG]**, {{INVOKE_ISSUE_TRACKER}} to log bugs:
 
 \`\`\`
-Use issue-tracker agent to:
 1. Check for duplicate bugs in the tracking system
    - The agent will automatically search for similar existing issues
    - It maintains memory of recently reported issues
@@ -3547,10 +3552,9 @@ Use issue-tracker agent to:
       role: "team-communicator",
       contentBlock: `#### Team Communication
 
-Use the team-communicator agent to share verification results (primarily for Slack trigger, but can be used for other triggers):
+{{INVOKE_TEAM_COMMUNICATOR}} to share verification results (primarily for Slack trigger, but can be used for other triggers):
 
 \`\`\`
-Use the team-communicator agent to:
 1. Post verification results summary
 2. Highlight critical failures that need immediate attention
 3. Share bugs logged with issue tracker links
@@ -6187,8 +6191,8 @@ var SUBAGENTS = {
     description: "Automatically create and track bugs and issues",
     icon: "bot",
     integrations: [
-      INTEGRATIONS.linear,
-      INTEGRATIONS.jira,
+      // INTEGRATIONS.linear,
+      // INTEGRATIONS.jira,
       INTEGRATIONS["jira-server"],
       INTEGRATIONS.notion,
       INTEGRATIONS.slack
@@ -6202,7 +6206,10 @@ var SUBAGENTS = {
     name: "Documentation Researcher",
     description: "Search and retrieve information from your documentation",
     icon: "file-search",
-    integrations: [INTEGRATIONS.notion, INTEGRATIONS.confluence],
+    integrations: [
+      INTEGRATIONS.notion
+      // INTEGRATIONS.confluence
+    ],
     model: "sonnet",
     color: "cyan",
     version: "1.0.0"
@@ -6285,6 +6292,62 @@ function buildSubagentsConfig(subagents) {
   return configs;
 }
 
+// src/core/tool-strings.ts
+var TOOL_STRINGS = {
+  "claude-code": {
+    INVOKE_TEST_RUNNER: "Use the test-runner subagent to execute the tests",
+    INVOKE_TEST_DEBUGGER_FIXER: "Use the test-debugger-fixer subagent to debug and fix the failing test",
+    INVOKE_TEST_CODE_GENERATOR: "Use the test-code-generator subagent to generate automated test code",
+    INVOKE_TEAM_COMMUNICATOR: "Use the team-communicator subagent to notify the team",
+    INVOKE_ISSUE_TRACKER: "Use the issue-tracker subagent to create or update issues",
+    INVOKE_DOCUMENTATION_RESEARCHER: "Use the documentation-researcher subagent to search and gather documentation"
+  },
+  "cursor": {
+    INVOKE_TEST_RUNNER: 'Run the test-runner agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/test-runner.md)" --output-format text\n```',
+    INVOKE_TEST_DEBUGGER_FIXER: 'Run the test-debugger-fixer agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/test-debugger-fixer.md)" --output-format text\n```',
+    INVOKE_TEST_CODE_GENERATOR: 'Run the test-code-generator agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/test-code-generator.md)" --output-format text\n```',
+    INVOKE_TEAM_COMMUNICATOR: 'Run the team-communicator agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/team-communicator.md)" --output-format text\n```',
+    INVOKE_ISSUE_TRACKER: 'Run the issue-tracker agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/issue-tracker.md)" --output-format text\n```',
+    INVOKE_DOCUMENTATION_RESEARCHER: 'Run the documentation-researcher agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/documentation-researcher.md)" --output-format text\n```'
+  },
+  "codex": {
+    INVOKE_TEST_RUNNER: 'Run the test-runner agent:\n```bash\ncodex -p "$(cat .codex/agents/test-runner.md)"\n```',
+    INVOKE_TEST_DEBUGGER_FIXER: 'Run the test-debugger-fixer agent:\n```bash\ncodex -p "$(cat .codex/agents/test-debugger-fixer.md)"\n```',
+    INVOKE_TEST_CODE_GENERATOR: 'Run the test-code-generator agent:\n```bash\ncodex -p "$(cat .codex/agents/test-code-generator.md)"\n```',
+    INVOKE_TEAM_COMMUNICATOR: 'Run the team-communicator agent:\n```bash\ncodex -p "$(cat .codex/agents/team-communicator.md)"\n```',
+    INVOKE_ISSUE_TRACKER: 'Run the issue-tracker agent:\n```bash\ncodex -p "$(cat .codex/agents/issue-tracker.md)"\n```',
+    INVOKE_DOCUMENTATION_RESEARCHER: 'Run the documentation-researcher agent:\n```bash\ncodex -p "$(cat .codex/agents/documentation-researcher.md)"\n```'
+  }
+};
+function getToolString(toolId, key) {
+  const toolStrings = TOOL_STRINGS[toolId];
+  if (!toolStrings) {
+    throw new Error(`Unknown tool: ${toolId}`);
+  }
+  const value = toolStrings[key];
+  if (!value) {
+    throw new Error(`Unknown string key: ${key} for tool: ${toolId}`);
+  }
+  return value;
+}
+function replaceInvocationPlaceholders(content, toolId) {
+  let result = content;
+  const keys = [
+    "INVOKE_TEST_RUNNER",
+    "INVOKE_TEST_DEBUGGER_FIXER",
+    "INVOKE_TEST_CODE_GENERATOR",
+    "INVOKE_TEAM_COMMUNICATOR",
+    "INVOKE_ISSUE_TRACKER",
+    "INVOKE_DOCUMENTATION_RESEARCHER"
+  ];
+  for (const key of keys) {
+    const placeholder = `{{${key}}}`;
+    const replacement = getToolString(toolId, key);
+    result = result.replace(new RegExp(placeholder, "g"), replacement);
+  }
+  return result;
+}
+
 // src/core/registry.ts
 async function getAgentConfiguration(taskDefinitions, projectSubAgents) {
   const taskSlugs = taskDefinitions.map((t) => t.slug);
@@ -6296,7 +6359,7 @@ async function getAgentConfiguration(taskDefinitions, projectSubAgents) {
   taskDefinitions.forEach((task) => {
     slashCommands[task.slug] = {
       frontmatter: task.frontmatter,
-      content: task.content
+      content: replaceInvocationPlaceholders(task.content, "claude-code")
     };
   });
   const allRoles = /* @__PURE__ */ new Set();