@bugzy-ai/bugzy 1.7.0 → 1.8.0

package/dist/index.cjs

@@ -157,8 +157,22 @@ var MCP_SERVERS = {
         RESEND_FROM_EMAIL: "${RESEND_FROM_EMAIL}"
       }
     }
+  },
+  github: {
+    provider: "github",
+    name: "GitHub",
+    description: "GitHub MCP server for PR and commit information",
+    requiresCredentials: true,
+    npmPackages: ["@bugzy-ai/github-mcp-server"],
+    config: {
+      command: "github-mcp-server",
+      args: [],
+      env: {
+        GITHUB_TOKEN: "${GITHUB_TOKEN}"
+      }
+    }
   }
-  // github: {
+  // github-modelcontextprotocol: {
   //   provider: 'github',
   //   name: 'GitHub',
   //   description: 'GitHub MCP server for repository operations',
@@ -1688,6 +1702,35 @@ CHANGE_CONTEXT = {
 }
 \`\`\``
     },
+    // Step 6b: Retrieve Code Change Details (conditional - changelog-historian)
+    {
+      inline: true,
+      title: "Retrieve Code Change Details",
+      content: `{{INVOKE_CHANGELOG_HISTORIAN}} to gather comprehensive context about recent code changes:
+
+Explore version control history related to the verification scope.
+
+Specifically gather:
+- Recent changes merged to the target branch
+- Change authors and contributors
+- Scope and impact of each change
+- Change descriptions and rationale
+- Related issues or tickets
+- Files and components affected
+
+The agent will:
+1. Check its memory for previously discovered repository context
+2. Explore version control for relevant changes
+3. Build comprehensive understanding of the change history
+4. Return synthesized change information
+
+Use this information to:
+- Identify which changes may have caused test failures
+- Understand the scope and risk of the changes
+- Enhance the verification report with change attribution
+- Provide better context for manual verification checklist`,
+      conditionalOnSubagent: "changelog-historian"
+    },
     // Step 7: Determine Test Scope (inline)
     {
       inline: true,
@@ -1982,7 +2025,7 @@ A successful verification includes:
     }
   ],
   requiredSubagents: ["test-runner", "test-debugger-fixer"],
-  optionalSubagents: ["documentation-researcher", "issue-tracker", "team-communicator"],
+  optionalSubagents: ["documentation-researcher", "issue-tracker", "team-communicator", "changelog-historian"],
   dependentTasks: []
 };
 
@@ -5083,6 +5126,128 @@ Maintain organized issue tracking:
 
 You are focused on creating clear, organized issue threads that leverage Slack's real-time collaboration features while maintaining comprehensive tracking in your memory. Your goal is to make issue management efficient and visible to the entire team while building knowledge about failure patterns to prevent future bugs.`;
 
+// src/subagents/templates/changelog-historian/github.ts
+var FRONTMATTER14 = {
+  name: "changelog-historian",
+  description: `Use this agent when you need to understand what code changes went into a build, deployment, or release. This agent retrieves PR and commit information from GitHub to help investigate test failures, regressions, or to understand what changed between releases. Examples: <example>Context: A test started failing after a deployment.
+user: "The checkout flow test is failing in staging. What changed recently?"
+assistant: "Let me use the changelog-historian agent to retrieve the recent PRs and commits that went into this build."
+<commentary>Since we need to understand what code changes may have caused the test failure, use the changelog-historian agent to retrieve PR and commit details from GitHub.</commentary></example> <example>Context: Need to understand changes between two releases.
+user: "What changed between v1.2.0 and v1.3.0?"
+assistant: "I'll use the changelog-historian agent to compare the two releases and list all the changes."
+<commentary>The agent will use GitHub comparison tools to show all commits and PRs between the two versions.</commentary></example>`,
+  model: "haiku",
+  color: "gray"
+};
+var CONTENT14 = `You are an expert Changelog Historian specializing in understanding code changes and their impact. Your primary responsibility is to retrieve and analyze PR and commit information from GitHub to help understand what changed in a codebase.
+
+## Core Responsibilities
+
+1. **Change Analysis**: You systematically gather information about code changes from GitHub PRs and commits to understand what modifications were made, when they occurred, and who made them.
+
+2. ${MEMORY_READ_INSTRUCTIONS.replace(/{ROLE}/g, "changelog-historian")}
+
+   **Memory Sections for Changelog Historian**:
+   - Repository information (owner, repo, default branch)
+   - Recent release tags and their commit SHAs
+   - Key PRs and their associated test impacts
+   - Known patterns of changes that cause specific types of failures
+   - Quick reference for common queries (last deployment, recent hotfixes)
+
+## Available GitHub Tools
+
+You have access to the following GitHub MCP tools:
+
+1. **github_list_prs**: List pull requests with filters
+   - Filter by state (open, closed, all)
+   - Filter by base branch (e.g., "main")
+   - Sort by created, updated, popularity, or long-running
+   - Pagination support
+
+2. **github_get_pr**: Get detailed PR information
+   - Files changed with additions/deletions
+   - Commits in the PR
+   - Labels, reviewers, and status
+
+3. **github_list_commits**: List commits on a branch
+   - Filter by date range (since, until)
+   - Get commit messages and authors
+   - Pagination support
+
+4. **github_get_commit**: Get detailed commit information
+   - Full list of file changes
+   - Stats (additions, deletions)
+   - Author and committer details
+
+5. **github_compare_commits**: Compare two refs
+   - See all commits between two points
+   - Get diff of file changes
+   - Understand what changed between releases
+
+## Operational Workflow
+
+1. **Initial Check**: Read \`.bugzy/runtime/memory/changelog-historian.md\` to load repository context and known patterns
+
+2. **Context Gathering**:
+   - Identify the repository owner and name from context or memory
+   - Determine the relevant time range or refs to analyze
+   - Use appropriate GitHub tools to gather change information
+
+3. **Change Analysis**:
+   - For recent failures: List recent merged PRs and commits
+   - For release comparison: Use compare_commits between tags/refs
+   - For specific issues: Find PRs/commits related to affected files
+
+4. ${MEMORY_UPDATE_INSTRUCTIONS.replace(/{ROLE}/g, "changelog-historian")}
+
+   Specifically for changelog-historian, consider updating:
+   - **Repository Config**: Store owner/repo if not already known
+   - **Release History**: Note significant release tags encountered
+   - **Impact Patterns**: Record correlations between changes and test impacts
+   - **Hotfix Tracking**: Note emergency fixes for future reference
+
+## Analysis Best Practices
+
+- Start with recent merged PRs when investigating failures
+- Cross-reference PR labels for context (bug, feature, hotfix)
+- Note file changes that overlap with failing test areas
+- Look for patterns in commit messages (conventional commits)
+- Track which changes went into specific environments
+
+## Query Response Approach
+
+1. Understand what period or refs the user is asking about
+2. Check memory for repository context and known patterns
+3. Use appropriate GitHub tools to gather change data
+4. Synthesize findings into a clear timeline or comparison
+5. Highlight changes most likely to impact the area of interest
+6. Update memory with new findings and patterns
+
+## Output Format
+
+When reporting changes, include:
+- PR number, title, and author
+- Merge date and target branch
+- Files changed with brief description
+- Relevance to the current investigation
+
+Example output:
+\`\`\`
+## Recent Changes (last 7 days)
+
+### PR #142: Fix checkout validation (merged 2 days ago)
+- Author: @developer
+- Files: src/checkout/validation.ts, tests/checkout.spec.ts
+- Relevance: HIGH - directly affects checkout flow
+
+### PR #140: Update dependencies (merged 3 days ago)
+- Author: @maintainer
+- Files: package.json, package-lock.json
+- Relevance: MEDIUM - may affect test stability
+\`\`\`
+
+You are meticulous about correlating code changes with observed behavior, helping teams quickly identify the root cause of issues by understanding what changed and when.`;
+
 // src/subagents/templates/index.ts
 var TEMPLATES = {
   "test-runner": {
@@ -5152,6 +5317,12 @@ var TEMPLATES = {
       frontmatter: FRONTMATTER13,
       content: CONTENT13
     }
+  },
+  "changelog-historian": {
+    github: {
+      frontmatter: FRONTMATTER14,
+      content: CONTENT14
+    }
   }
 };
 function getTemplate(role, integration) {
@@ -5235,6 +5406,13 @@ var INTEGRATIONS = {
     integrationType: "local"
     // Uses platform API key, no OAuth needed
   },
+  github: {
+    id: "github",
+    name: "GitHub",
+    provider: "github",
+    requiredMCP: "mcp__github__*",
+    integrationType: "oauth"
+  },
   local: {
     id: "local",
     name: "Local (Terminal)",
@@ -5322,6 +5500,17 @@ var SUBAGENTS = {
     isRequired: true,
     // Required for automated test execution and fixing
     version: "1.0.0"
+  },
+  "changelog-historian": {
+    role: "changelog-historian",
+    name: "Changelog Historian",
+    description: "Retrieves and analyzes code changes from GitHub PRs and commits",
+    icon: "git-pull-request",
+    integrations: [INTEGRATIONS.github],
+    model: "haiku",
+    color: "gray",
+    isRequired: false,
+    version: "1.0.0"
   }
 };
 function getAllSubAgents() {
@@ -5386,7 +5575,8 @@ var TOOL_STRINGS = {
     INVOKE_TEAM_COMMUNICATOR: '**DELEGATE TO SUBAGENT**: Use the Task tool with `subagent_type: "team-communicator"` to send team notifications.\nThe agent will post to Slack/Teams/Email. Include message content and context in the prompt.',
     INLINE_TEAM_COMMUNICATOR: "**TEAM COMMUNICATION**: Read `.claude/agents/team-communicator.md` and follow its instructions to communicate with the team.\nUse the tools and guidelines specified in that file within this context. Do NOT spawn a sub-agent.",
     INVOKE_ISSUE_TRACKER: '**DELEGATE TO SUBAGENT**: Use the Task tool with `subagent_type: "issue-tracker"` to create/update issues.\nThe agent will interact with Jira. Include bug details and classification in the prompt.',
-    INVOKE_DOCUMENTATION_RESEARCHER: '**DELEGATE TO SUBAGENT**: Use the Task tool with `subagent_type: "documentation-researcher"` to search docs.\nThe agent will search Notion/Confluence. Include search query and context in the prompt.'
+    INVOKE_DOCUMENTATION_RESEARCHER: '**DELEGATE TO SUBAGENT**: Use the Task tool with `subagent_type: "documentation-researcher"` to search docs.\nThe agent will search Notion/Confluence. Include search query and context in the prompt.',
+    INVOKE_CHANGELOG_HISTORIAN: '**DELEGATE TO SUBAGENT**: Use the Task tool with `subagent_type: "changelog-historian"` to retrieve change history.\nThe agent will query GitHub for PRs and commits. Include repo context and date range in the prompt.'
   },
   "cursor": {
     INVOKE_TEST_RUNNER: 'Run the test-runner agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/test-runner.md)" --output-format text\n```',
@@ -5395,7 +5585,8 @@ var TOOL_STRINGS = {
     INVOKE_TEAM_COMMUNICATOR: 'Run the team-communicator agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/team-communicator.md)" --output-format text\n```',
     INLINE_TEAM_COMMUNICATOR: "**TEAM COMMUNICATION**: Read `.cursor/agents/team-communicator.md` and follow its instructions to communicate with the team.\nUse the tools and guidelines specified in that file within this context.",
     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```'
+    INVOKE_DOCUMENTATION_RESEARCHER: 'Run the documentation-researcher agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/documentation-researcher.md)" --output-format text\n```',
+    INVOKE_CHANGELOG_HISTORIAN: 'Run the changelog-historian agent:\n```bash\ncursor-agent -p "$(cat .cursor/agents/changelog-historian.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```',
@@ -5404,7 +5595,8 @@ var TOOL_STRINGS = {
     INVOKE_TEAM_COMMUNICATOR: 'Run the team-communicator agent:\n```bash\ncodex -p "$(cat .codex/agents/team-communicator.md)"\n```',
     INLINE_TEAM_COMMUNICATOR: "**TEAM COMMUNICATION**: Read `.codex/agents/team-communicator.md` and follow its instructions to communicate with the team.\nUse the tools and guidelines specified in that file within this context.",
     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```'
+    INVOKE_DOCUMENTATION_RESEARCHER: 'Run the documentation-researcher agent:\n```bash\ncodex -p "$(cat .codex/agents/documentation-researcher.md)"\n```',
+    INVOKE_CHANGELOG_HISTORIAN: 'Run the changelog-historian agent:\n```bash\ncodex -p "$(cat .codex/agents/changelog-historian.md)"\n```'
   }
 };
 function getToolString(toolId, key) {
@@ -5426,7 +5618,8 @@ function replaceInvocationPlaceholders(content, toolId, isLocal = false) {
     "INVOKE_TEST_CODE_GENERATOR",
     "INVOKE_TEAM_COMMUNICATOR",
     "INVOKE_ISSUE_TRACKER",
-    "INVOKE_DOCUMENTATION_RESEARCHER"
+    "INVOKE_DOCUMENTATION_RESEARCHER",
+    "INVOKE_CHANGELOG_HISTORIAN"
   ];
   for (const key of keys) {
     const placeholder = `{{${key}}}`;