GitHub Manager Tools

Complete guide to using GitHub Manager voice tools for repository management

The GitHub Manager provides a comprehensive set of voice-activated tools for managing GitHub repositories, issues, pull requests, and more. Each tool is designed to be triggered by natural language commands and specific keywords.

Repository Management

Get User Repositories

Tool: get_user_repositories

Description: Retrieve a list of repositories for the authenticated user.

Trigger phrases:

  • "Show my repositories"
  • "List my GitHub repos"
  • "What repos do I have?"
  • "Show my private/public repositories"
  • "Get my latest repositories"

Parameters:

  • visibility: Filter by repository visibility (all, public, private)
  • affiliation: Filter by user affiliation (owner, collaborator, organization_member)
  • sort: Sort repositories by (created, updated, pushed, full_name)
  • per_page: Number of results per page

Get Repository Details

Tool: get_repository_details

Description: Get comprehensive information about a specific repository.

Trigger phrases:

  • "Show details for [repo name]"
  • "Tell me about the [owner]/[repo] repository"
  • "What's the status of [repo]?"
  • "Get information about [repo]"
  • "Describe [repo] repository"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)

Get Repository Contents

Tool: get_repository_contents

Description: Browse the contents of a directory or file in a repository.

Trigger phrases:

  • "Show me the files in [repo]"
  • "List contents of [path] in [repo]"
  • "What's in the [folder] directory?"
  • "Browse [repo] repository structure"
  • "Show me the root directory of [repo]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • path: Path to directory or file (optional, defaults to root)
  • ref: Branch or commit ref (optional, defaults to default branch)

Get File Content

Tool: get_file_content

Description: Retrieve the raw content of a specific file in a repository.

Trigger phrases:

  • "Show me the contents of [file]"
  • "Read [file] from [repo]"
  • "Get the code from [file]"
  • "Display [file] content"
  • "Open [file] in [repo]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • path: Path to the file (required)
  • ref: Branch or commit ref (optional)

Get Repository Tree

Tool: get_repository_tree

Description: Get the complete Git tree structure of a repository.

Trigger phrases:

  • "Show me the full structure of [repo]"
  • "Get the complete file tree"
  • "Display repository hierarchy"
  • "Show all files and folders in [repo]"
  • "Map out the project structure"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • tree_sha: Tree SHA or branch name (optional, defaults to default branch)
  • recursive: Get tree recursively (optional, defaults to true)

Search Repository Code

Tool: search_repository_code

Description: Search for code patterns, functions, or text within a repository.

Trigger phrases:

  • "Search for [term] in [repo]"
  • "Find [function name] in the code"
  • "Look for [pattern] in [repo]"
  • "Search [repo] for [keyword]"
  • "Find all occurrences of [text]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • query: Search query (required)
  • path: Limit search to specific path
  • language: Filter by programming language
  • per_page: Results per page

Analyze Code Structure

Tool: analyze_code_structure

Description: Provide insights about project organization, architecture, and patterns.

Trigger phrases:

  • "Analyze the structure of [repo]"
  • "What's the architecture of this project?"
  • "Give me insights about [repo]"
  • "Analyze [repo] codebase"
  • "Describe the project organization"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • include_dependencies: Include dependency analysis (optional)

Get Repository Branches

Tool: get_repository_branches

Description: List all branches in a repository.

Trigger phrases:

  • "Show branches in [repo]"
  • "List all branches"
  • "What branches exist in [repo]?"
  • "Get branch list for [repo]"
  • "Show me the available branches"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)

Get Repository Labels

Tool: get_repository_labels

Description: Get all labels available in a repository.

Trigger phrases:

  • "Show labels for [repo]"
  • "List issue labels"
  • "What labels are available?"
  • "Get all labels in [repo]"
  • "Show me the label options"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)

Issue Management

Get Repository Issues

Tool: get_repository_issues

Description: Retrieve issues for a specific repository with filtering options.

Trigger phrases:

  • "Show issues in [repo]"
  • "List all open issues"
  • "Get issues with [label] label"
  • "Show closed issues"
  • "What issues need attention?"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • state: Filter by state (open, closed, all)
  • labels: Filter by labels (comma-separated)
  • sort: Sort by (created, updated, comments)
  • direction: Sort direction (asc, desc)
  • per_page: Results per page

Get Issue Details

Tool: get_issue_details

Description: Get complete information about a specific issue.

Trigger phrases:

  • "Show me issue #[number]"
  • "Get details for issue [number]"
  • "What's the status of issue #[number]?"
  • "Tell me about issue [number]"
  • "Open issue number [number]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • issue_number: Issue number (required)

Create Issue

Tool: create_issue

Description: Create a new issue in a repository. Automatically mentions @claude in the description.

Trigger phrases:

  • "Create a new issue"
  • "Open an issue about [topic]"
  • "Report a bug"
  • "File an issue for [problem]"
  • "Create issue titled [title]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • title: Issue title (required)
  • body: Issue description
  • labels: Labels to apply
  • assignees: Users to assign

Update Issue

Tool: update_issue

Description: Modify an existing issue. Automatically mentions @claude in updates.

Trigger phrases:

  • "Update issue #[number]"
  • "Change issue [number] title"
  • "Close issue #[number]"
  • "Reopen issue [number]"
  • "Add labels to issue [number]"
  • "Assign issue [number] to [user]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • issue_number: Issue number (required)
  • title: New title
  • body: New description
  • state: Change state (open, closed)
  • labels: Update labels
  • assignees: Update assignees

Add Issue Comment

Tool: add_issue_comment

Description: Add a comment to an issue or pull request. Automatically mentions @claude.

Trigger phrases:

  • "Comment on issue #[number]"
  • "Add a comment to issue [number]"
  • "Reply to issue [number]"
  • "Post comment on PR #[number]"
  • "Respond to issue [number]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • issue_number: Issue or PR number (required)
  • body: Comment text (required)

Get Issue Comments

Tool: get_issue_comments

Description: Retrieve all comments for an issue or pull request.

Trigger phrases:

  • "Show comments on issue #[number]"
  • "Get issue [number] comments"
  • "Read comments for PR #[number]"
  • "List all comments on issue [number]"
  • "What are people saying about issue [number]?"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • issue_number: Issue or PR number (required)

Get Issue Comment

Tool: get_issue_comment

Description: Get details about a specific comment by its ID.

Trigger phrases:

  • "Show comment [id]"
  • "Get comment with ID [id]"
  • "Read specific comment [id]"
  • "Display comment number [id]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • comment_id: Comment ID (required)

Pull Request Management

Get Pull Requests

Tool: get_pull_requests

Description: List pull requests for a repository with filtering options.

Trigger phrases:

  • "Show pull requests"
  • "List open PRs"
  • "Get PRs for [repo]"
  • "Show merged pull requests"
  • "What PRs need review?"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • state: Filter by state (open, closed, all)
  • head: Filter by head branch
  • base: Filter by base branch
  • sort: Sort by (created, updated, popularity)
  • direction: Sort direction (asc, desc)
  • per_page: Results per page

Get Pull Request Details

Tool: get_pull_request_details

Description: Get comprehensive information about a specific pull request.

Trigger phrases:

  • "Show PR #[number]"
  • "Get pull request [number] details"
  • "What's the status of PR [number]?"
  • "Tell me about pull request [number]"
  • "Review PR number [number]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • pr_number: Pull request number (required)

Create Pull Request

Tool: create_pull_request

Description: Create a new pull request. Automatically mentions @claude in the description.

Trigger phrases:

  • "Create a pull request"
  • "Open a PR from [branch] to [base]"
  • "Submit PR for review"
  • "Create pull request titled [title]"
  • "Merge [head] into [base]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • title: PR title (required)
  • head: Head branch (required)
  • base: Base branch (required)
  • body: PR description
  • draft: Create as draft PR

Update Pull Request

Tool: update_pull_request

Description: Modify an existing pull request. Automatically mentions @claude.

Trigger phrases:

  • "Update PR #[number]"
  • "Change pull request [number] title"
  • "Close PR [number]"
  • "Edit pull request [number]"
  • "Modify PR description"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • pr_number: Pull request number (required)
  • title: New title
  • body: New description
  • state: Change state (open, closed)

PR Monitoring

Start PR Monitoring

Tool: start_pr_monitoring

Description: Begin monitoring a repository for new pull requests with voice notifications.

Trigger phrases:

  • "Start monitoring [repo] for PRs"
  • "Watch [repo] for new pull requests"
  • "Alert me about new PRs in [repo]"
  • "Monitor pull requests"
  • "Track new PRs in [repo]"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)
  • checkIntervalMs: Check interval in milliseconds (optional, default: 30000)
  • voiceAnnouncements: Enable voice notifications (optional, default: true)

Stop PR Monitoring

Tool: stop_pr_monitoring

Description: Stop monitoring a repository for pull requests.

Trigger phrases:

  • "Stop monitoring [repo]"
  • "Stop watching PRs"
  • "Disable PR alerts for [repo]"
  • "Turn off PR monitoring"
  • "Stop tracking pull requests"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)

Check PR Monitoring Status

Tool: check_pr_monitoring_status

Description: View the current PR monitoring status for all or specific repositories.

Trigger phrases:

  • "What repos am I monitoring?"
  • "Show monitoring status"
  • "Check PR monitoring for [repo]"
  • "List monitored repositories"
  • "Am I watching [repo]?"

Parameters:

  • owner: Repository owner (optional)
  • repo: Repository name (optional)

Manually Check New PRs

Tool: manually_check_new_prs

Description: Perform a one-time check for new pull requests.

Trigger phrases:

  • "Check for new PRs now"
  • "Any new pull requests in [repo]?"
  • "Manually check [repo] for PRs"
  • "Look for recent PRs"
  • "Quick check for pull requests"

Parameters:

  • owner: Repository owner username (required)
  • repo: Repository name (required)

Navigation Tools

Navigate to Ticket

Tool: navigate_to_ticket

Description: Navigate directly to a GitHub issue or pull request by number.

Trigger phrases:

  • "Go to issue #[number]"
  • "Open ticket [number]"
  • "Navigate to PR [number]"
  • "Show me issue number [number]"
  • "Take me to pull request [number]"

Parameters:

  • ticket_number: Issue or PR number (required)
  • reason: Reason for navigation

Navigate to Path

Tool: navigate_to_path

Description: Navigate to specific application paths and pages.

Trigger phrases:

  • "Go to [page name]"
  • "Navigate to settings"
  • "Open the dashboard"
  • "Take me to [section]"
  • "Show me the [page]"

Parameters:

  • path: Application path (required)
  • query: Query parameters
  • reason: Navigation reason

List App Routes

Tool: list_app_routes

Description: Display all available application routes and navigation options.

Trigger phrases:

  • "What pages can I navigate to?"
  • "Show available routes"
  • "List all pages"
  • "What navigation options are there?"
  • "Show me all available paths"

Parameters: None

In-Page Navigation

Tool: in_page_navigation

Description: Control scrolling and navigation within the current page.

Trigger phrases:

  • "Scroll down"
  • "Go to the top"
  • "Scroll to bottom"
  • "Page up/down"
  • "Scroll to [element]"

Parameters:

  • action: Navigation action (scroll_down, scroll_up, page_down, page_up, scroll_to_top, scroll_to_bottom, scroll_to_element)
  • selector: CSS selector for scroll_to_element
  • amount: Scroll amount in pixels

Return to Conversation

Tool: return_to_conversation

Description: Return to the voice conversation interface after navigating away.

Trigger phrases:

  • "Go back to conversation"
  • "Return to voice chat"
  • "Take me back"
  • "Back to the conversation"
  • "Return to main screen"

Parameters:

  • reason: Reason for returning

System Management

Reset Agent State

Tool: reset_agent_state

Description: Clear various types of agent state and context for a fresh start.

Trigger phrases:

  • "Reset the agent"
  • "Clear all state"
  • "Start fresh"
  • "Clear conversation history"
  • "Reset workspace"

Parameters:

  • clearWorkspace: Clear workspace data (default: true)
  • clearConversation: Clear conversation history (default: true)
  • clearEventLogs: Clear event logs (default: true)
  • clearNavigationHistory: Clear navigation history (default: true)
  • clearToolCallHistory: Clear tool call history (default: true)
  • clearPRMonitoring: Clear PR monitoring state (default: false)
  • clearAuthentication: Clear authentication tokens (default: false)
  • clearUserPreferences: Clear user preferences (default: false)
  • clearCache: Clear caches (default: true)
  • clearTempFiles: Clear temporary files (default: true)

Tips for Effective Use

  1. Natural Language: The tools are designed to understand natural language. You don't need to use exact phrases.

  2. Context Awareness: The agent remembers context from your conversation, so you can refer to "the repository" or "that issue" after mentioning it once.

  3. Automatic Mentions: When creating or updating issues, PRs, and comments, the agent automatically includes @claude mentions to maintain traceability.

  4. Voice Feedback: Many tools provide voice feedback when operations complete, especially for monitoring and navigation tasks.

  5. Chaining Operations: You can chain multiple operations together, like "Create an issue about the bug we just discussed and assign it to me."

  6. Smart Defaults: Most optional parameters have sensible defaults, so you only need to specify what you want to change.

  7. Error Handling: The agent will provide helpful error messages if something goes wrong and suggest alternatives when possible.

Common Workflows

Bug Reporting Workflow

  1. "Create an issue titled 'Button not working on mobile'"
  2. "Add the bug and high-priority labels"
  3. "Assign it to the mobile team"

PR Review Workflow

  1. "Show me open pull requests"
  2. "Get details for PR #42"
  3. "Show me the changes in PR #42"
  4. "Add a comment approving the changes"

Repository Exploration

  1. "Show me the repository structure"
  2. "Search for authentication code"
  3. "Show me the contents of the auth folder"
  4. "Get the file content of login.js"

Monitoring Setup

  1. "Start monitoring my-repo for new PRs"
  2. "Check monitoring status"
  3. "Alert me with voice when new PRs arrive"
  4. "Stop monitoring when done"