@ldraney/github-mcp 0.1.0 → 0.2.0-beta.1

package/dist/index.js

@@ -2,6 +2,7 @@
 import { Command } from 'commander';
 import { getToken, login, logout, getAuthStatus } from './auth/oauth-flow.js';
 import { startServer } from './server.js';
+import { ToolGenerator } from './tools/generator.js';
 const program = new Command();
 program
     .name('github-mcp')
@@ -9,7 +10,8 @@ program
     .version('0.1.0');
 // Default command: start server
 program
-    .action(async () => {
+    .option('-c, --categories <categories>', `Comma-separated list of tool categories to load (available: ${ToolGenerator.getAvailableCategories().join(', ')})`)
+    .action(async (options) => {
     try {
         let token = await getToken();
         if (!token) {
@@ -20,7 +22,11 @@ program
             console.error('Authentication failed. Cannot start server.');
             process.exit(1);
         }
-        await startServer(token);
+        // Parse categories if provided
+        const categories = options.categories
+            ? options.categories.split(',').map((c) => c.trim())
+            : undefined;
+        await startServer(token, { categories });
     }
     catch (error) {
         console.error('Error:', error instanceof Error ? error.message : error);

package/dist/prompts/activity-summary.d.ts

@@ -0,0 +1,10 @@
+import type { Prompt, GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+/**
+ * Activity summary prompt definitions
+ */
+export declare const activityPrompts: Prompt[];
+/**
+ * Generate a prompt result for activity summaries
+ * These prompts instruct Claude to use the activity tools to fetch and summarize events
+ */
+export declare function getActivityPrompt(name: string, args: Record<string, string>): GetPromptResult;

package/dist/prompts/activity-summary.js

@@ -0,0 +1,154 @@
+/**
+ * Activity summary prompt definitions
+ */
+export const activityPrompts = [
+    {
+        name: 'daily_summary',
+        description: 'Summarize GitHub activity from the last 24 hours for a repository',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+        ],
+    },
+    {
+        name: 'weekly_summary',
+        description: 'Summarize GitHub activity from the last 7 days for a repository',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+        ],
+    },
+    {
+        name: 'repo_activity',
+        description: 'Get recent activity summary for a repository (configurable timeframe)',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+            {
+                name: 'days',
+                description: 'Number of days to look back (default: 7)',
+                required: false,
+            },
+        ],
+    },
+];
+/**
+ * Generate a prompt result for activity summaries
+ * These prompts instruct Claude to use the activity tools to fetch and summarize events
+ */
+export function getActivityPrompt(name, args) {
+    const owner = args.owner;
+    const repo = args.repo;
+    switch (name) {
+        case 'daily_summary':
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please summarize the GitHub activity for ${owner}/${repo} from the last 24 hours.
+
+Use the github_activity_list_repo_events tool to fetch recent events for this repository, then provide a summary that includes:
+
+1. **Commits**: Any push events with commit messages
+2. **Pull Requests**: Opened, closed, or merged PRs
+3. **Issues**: New issues or issue comments
+4. **Reviews**: PR reviews and review comments
+5. **Releases**: Any new releases or tags
+
+Filter the events to only include those from the last 24 hours based on the created_at timestamp.
+
+If there's no activity, say so clearly.`,
+                        },
+                    },
+                ],
+            };
+        case 'weekly_summary':
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please summarize the GitHub activity for ${owner}/${repo} from the last 7 days.
+
+Use the github_activity_list_repo_events tool to fetch recent events for this repository (you may need to paginate through results), then provide a comprehensive summary that includes:
+
+1. **Commits**: Push events with notable commit messages grouped by author
+2. **Pull Requests**: Opened, closed, or merged PRs with titles
+3. **Issues**: New issues, closed issues, and notable issue discussions
+4. **Reviews**: PR reviews and their outcomes
+5. **Releases**: Any new releases with version numbers
+6. **Contributors**: Active contributors during this period
+
+Filter the events to only include those from the last 7 days based on the created_at timestamp.
+
+Organize the summary by category and highlight the most significant changes.`,
+                        },
+                    },
+                ],
+            };
+        case 'repo_activity':
+            const days = parseInt(args.days) || 7;
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please summarize the GitHub activity for ${owner}/${repo} from the last ${days} day(s).
+
+Use the github_activity_list_repo_events tool to fetch recent events for this repository, then provide a summary that includes:
+
+1. **Overview**: Quick stats on total events by type
+2. **Commits**: Notable push events and commit activity
+3. **Pull Requests**: PR activity (opened, closed, merged)
+4. **Issues**: Issue activity (opened, closed, commented)
+5. **Other Events**: Any other notable activity (releases, forks, stars, etc.)
+
+Filter the events to only include those from the last ${days} day(s) based on the created_at timestamp.
+
+Present the information in a clear, scannable format.`,
+                        },
+                    },
+                ],
+            };
+        default:
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Unknown prompt: ${name}`,
+                        },
+                    },
+                ],
+            };
+    }
+}

package/dist/prompts/code-review.d.ts

@@ -0,0 +1,9 @@
+import type { Prompt, GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+/**
+ * Code review prompt definitions
+ */
+export declare const codeReviewPrompts: Prompt[];
+/**
+ * Generate a prompt result for code review
+ */
+export declare function getCodeReviewPrompt(name: string, args: Record<string, string>): GetPromptResult | null;

package/dist/prompts/code-review.js

@@ -0,0 +1,145 @@
+/**
+ * Code review prompt definitions
+ */
+export const codeReviewPrompts = [
+    {
+        name: 'code_review',
+        description: 'Review a pull request with detailed suggestions and feedback',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+            {
+                name: 'pull_number',
+                description: 'Pull request number',
+                required: true,
+            },
+            {
+                name: 'focus',
+                description: 'Review focus area (e.g., security, performance, style, all)',
+                required: false,
+            },
+        ],
+    },
+    {
+        name: 'pr_summary',
+        description: 'Generate a concise summary of a pull request',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+            {
+                name: 'pull_number',
+                description: 'Pull request number',
+                required: true,
+            },
+        ],
+    },
+];
+/**
+ * Generate a prompt result for code review
+ */
+export function getCodeReviewPrompt(name, args) {
+    const owner = args.owner;
+    const repo = args.repo;
+    const pullNumber = args.pull_number;
+    switch (name) {
+        case 'code_review':
+            const focus = args.focus || 'all';
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please review pull request #${pullNumber} in ${owner}/${repo}.
+
+First, use these tools to gather information:
+1. github_pulls_get - Get PR details (title, description, state)
+2. github_pulls_list_files - Get the list of changed files
+3. github_pulls_list_commits - Get commits in this PR
+
+Then provide a comprehensive code review with focus on: ${focus === 'all' ? 'all aspects' : focus}
+
+Structure your review as follows:
+
+## Summary
+Brief overview of what this PR does.
+
+## Changes Analysis
+List the files changed with a brief description of each change.
+
+## Review Feedback
+
+${focus === 'all' || focus === 'security' ? `### Security
+- Check for potential vulnerabilities (injection, XSS, auth issues, etc.)
+- Review sensitive data handling
+- Check for hardcoded credentials or secrets
+` : ''}
+${focus === 'all' || focus === 'performance' ? `### Performance
+- Identify potential bottlenecks
+- Check for inefficient algorithms or queries
+- Review resource usage
+` : ''}
+${focus === 'all' || focus === 'style' ? `### Code Style & Quality
+- Check naming conventions
+- Review code organization
+- Suggest readability improvements
+` : ''}
+### Logic & Correctness
+- Verify the implementation matches the PR description
+- Check edge cases
+- Identify potential bugs
+
+## Suggestions
+Specific, actionable suggestions for improvement.
+
+## Verdict
+Overall assessment: Approve, Request Changes, or Comment.`,
+                        },
+                    },
+                ],
+            };
+        case 'pr_summary':
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please provide a concise summary of pull request #${pullNumber} in ${owner}/${repo}.
+
+Use these tools:
+1. github_pulls_get - Get PR details
+2. github_pulls_list_files - Get changed files
+3. github_pulls_list_commits - Get commits
+
+Provide a summary that includes:
+- **Title & Purpose**: What does this PR do?
+- **Files Changed**: List of files with change type (added/modified/deleted)
+- **Key Changes**: Bullet points of the main changes
+- **Size**: Lines added/removed, number of files
+
+Keep it brief - this is for quick understanding, not a full review.`,
+                        },
+                    },
+                ],
+            };
+        default:
+            return null;
+    }
+}

package/dist/prompts/issue-triage.d.ts

@@ -0,0 +1,9 @@
+import type { Prompt, GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+/**
+ * Issue triage prompt definitions
+ */
+export declare const issueTriagePrompts: Prompt[];
+/**
+ * Generate a prompt result for issue triage
+ */
+export declare function getIssueTriagePrompt(name: string, args: Record<string, string>): GetPromptResult | null;

package/dist/prompts/issue-triage.js

@@ -0,0 +1,202 @@
+/**
+ * Issue triage prompt definitions
+ */
+export const issueTriagePrompts = [
+    {
+        name: 'issue_triage',
+        description: 'Analyze and categorize a GitHub issue with suggested labels and priority',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+            {
+                name: 'issue_number',
+                description: 'Issue number to triage',
+                required: true,
+            },
+        ],
+    },
+    {
+        name: 'issue_batch_triage',
+        description: 'Triage multiple open issues and suggest prioritization',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+            {
+                name: 'limit',
+                description: 'Number of issues to triage (default: 10)',
+                required: false,
+            },
+        ],
+    },
+    {
+        name: 'find_duplicates',
+        description: 'Find potential duplicate issues in a repository',
+        arguments: [
+            {
+                name: 'owner',
+                description: 'Repository owner (username or organization)',
+                required: true,
+            },
+            {
+                name: 'repo',
+                description: 'Repository name',
+                required: true,
+            },
+            {
+                name: 'issue_number',
+                description: 'Issue number to find duplicates for',
+                required: true,
+            },
+        ],
+    },
+];
+/**
+ * Generate a prompt result for issue triage
+ */
+export function getIssueTriagePrompt(name, args) {
+    const owner = args.owner;
+    const repo = args.repo;
+    switch (name) {
+        case 'issue_triage':
+            const issueNumber = args.issue_number;
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please triage issue #${issueNumber} in ${owner}/${repo}.
+
+Use these tools:
+1. github_issues_get - Get issue details
+2. github_issues_list_comments - Get any discussion
+3. github_issues_list_labels - Get available labels in the repo
+
+Provide a triage report:
+
+## Issue Summary
+Brief description of what the issue is about.
+
+## Classification
+- **Type**: Bug, Feature Request, Documentation, Question, or Other
+- **Severity**: Critical, High, Medium, or Low
+- **Effort Estimate**: Small, Medium, Large, or Unknown
+
+## Suggested Labels
+Based on available labels in the repo, suggest which labels to apply.
+
+## Priority Assessment
+Explain why this issue should be prioritized at a certain level.
+
+## Additional Context
+- Is more information needed from the reporter?
+- Are there related issues that should be linked?
+- Who might be a good assignee based on the problem area?
+
+## Recommended Next Steps
+What should happen next with this issue?`,
+                        },
+                    },
+                ],
+            };
+        case 'issue_batch_triage':
+            const limit = parseInt(args.limit) || 10;
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please triage the open issues in ${owner}/${repo}.
+
+Use these tools:
+1. github_issues_list - Get open issues (limit: ${limit}, state: open)
+2. github_issues_list_labels - Get available labels
+
+For each issue, provide a brief triage:
+
+## Issues Overview
+
+Create a table with:
+| # | Title | Type | Severity | Effort | Suggested Labels |
+|---|-------|------|----------|--------|------------------|
+
+## Priority Ranking
+List the issues in recommended priority order with brief justification.
+
+## Quick Wins
+Identify any issues that are low effort but high value.
+
+## Needs Attention
+Flag any issues that:
+- Are stale and need follow-up
+- Need more information
+- Might be duplicates
+
+## Recommended Actions
+Suggest immediate actions to improve issue hygiene.`,
+                        },
+                    },
+                ],
+            };
+        case 'find_duplicates':
+            const targetIssue = args.issue_number;
+            return {
+                messages: [
+                    {
+                        role: 'user',
+                        content: {
+                            type: 'text',
+                            text: `Please find potential duplicate issues for #${targetIssue} in ${owner}/${repo}.
+
+Use these tools:
+1. github_issues_get - Get the target issue details
+2. github_issues_list - Get other open issues to compare
+3. github_search_issues_and_pull_requests - Search for similar issues by keywords
+
+Process:
+1. Read issue #${targetIssue} to understand what it's about
+2. Extract key terms and concepts
+3. Search for issues with similar terms
+4. Compare and identify potential duplicates
+
+Report format:
+
+## Target Issue
+Brief summary of #${targetIssue}
+
+## Potential Duplicates
+For each potential duplicate:
+- **Issue #X**: Title
+  - Similarity: High/Medium/Low
+  - Reason: Why it might be a duplicate
+  - Key differences: What's different
+
+## Recommendation
+- Which issues (if any) should be marked as duplicates
+- Which issue should be kept as the primary
+- Any issues that are related but not duplicates`,
+                        },
+                    },
+                ],
+            };
+        default:
+            return null;
+    }
+}

package/dist/prompts/release-notes.d.ts

@@ -0,0 +1,9 @@
+import type { Prompt, GetPromptResult } from '@modelcontextprotocol/sdk/types.js';
+/**
+ * Release notes prompt definitions
+ */
+export declare const releaseNotesPrompts: Prompt[];
+/**
+ * Generate a prompt result for release notes
+ */
+export declare function getReleaseNotesPrompt(name: string, args: Record<string, string>): GetPromptResult | null;