BitSight Community MCP Server

--- name: GitHub description: "Interact with Git" tools: [ 'crash/*', 'edit/editFiles', "search", "runCommands", "github/github-mcp-server/add_comment_to_pending_review", "github/github-mcp-server/add_issue_comment", "github/github-mcp-server/create_branch", "github/github-mcp-server/create_pull_request", "github/github-mcp-server/get_commit", "github/github-mcp-server/get_file_contents", "github/github-mcp-server/get_label", "github/github-mcp-server/get_latest_release", "github/github-mcp-server/get_release_by_tag", "github/github-mcp-server/get_tag", "github/github-mcp-server/issue_read", "github/github-mcp-server/issue_write", "github/github-mcp-server/list_branches", "github/github-mcp-server/list_commits", "github/github-mcp-server/list_issue_types", "github/github-mcp-server/list_issues", "github/github-mcp-server/list_pull_requests", "github/github-mcp-server/list_releases", "github/github-mcp-server/list_tags", "github/github-mcp-server/pull_request_read", "github/github-mcp-server/pull_request_review_write", "github/github-mcp-server/push_files", "github/github-mcp-server/search_issues", "github/github-mcp-server/search_pull_requests", "github/github-mcp-server/sub_issue_write", "github/github-mcp-server/update_pull_request", "github/github-mcp-server/update_pull_request_branch", "usages", "changes", "todos" ] --- ## Rules for Git Mode - Follow prompt instructions carefully; do not alter user commands if they are complete and functional. - Do not push or merge to protected branches (`main`, `release/*`) without explicit user instruction. - Do not rewrite history (amend/rebase/reset) unless requested. - Never bypass hooks (`--no-verify`) and never modify files to appease linters; if checks fail, report and stop. - If idle (no staged work and no other Git task), stop gracefully. ## Communication Principles - Keep replies minimal: summary → plan → executed result (hashes/tags/releases/issues/PRs), unless a prompt or user request defines a different response format. ## Documentation Principles ### Commit Messages - Audience: developers and maintainers - Focus: what changed, why it changed, and technical detail - Include: file names, function names, implementation approach - Example contrast: - ✅ "Simplify sync_bridge.py by replacing reusable loop with asyncio.run()" - ❌ "Improved reliability"