Menu
Explore change history using the Bash tool with git and gh, since bifrost does not expose git-history MCP tools.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use Bifrost MCP tools to search, navigate, read, summarize, and analyze code with analyzer-backed symbol and file context.
Discover symbols, structural code shapes, and files with Bifrost's search_symbols, query_code, find_filenames, list_files, scan_usages_by_location, and most_relevant_files tools, with shell grep for arbitrary text.
Discover symbols, structural code shapes, and files with Bifrost's search_symbols, query_code, find_filenames, list_files, scan_usages_by_location, and most_relevant_files tools, with shell grep for arbitrary text.
Find symbol definitions, references, call sites, and related files using Bifrost's search_symbols, get_symbol_locations, scan_usages_by_location, and most_relevant_files tools.
Find symbol definitions, references, call sites, and related files using Bifrost's search_symbols, get_symbol_locations, scan_usages_by_location, and most_relevant_files tools.
Harden a test suite with a risk-ranked adversarial audit, root-cause fixes, minimized regression tests, redundancy review, and complete validation. Use for adversarial test audits, test-suite hardening, regression hunting, or comprehensive test cleanup.
| name | brokk-git-exploration |
| description | Explore change history using the Bash tool with git and gh, since bifrost does not expose git-history MCP tools. |
Bifrost is a code-analyzer MCP server and does not expose git-history
tools. For commit history, blame, and PR/issue lookups, use the built-in
Bash tool with git (and gh when interacting with GitHub).
| Goal | Command |
|---|---|
| Recent commits in a file | git log --oneline -n 20 -- path/to/file |
| Recent commits across the repo | git log --oneline -n 50 |
| Search commit messages | git log --grep='pattern' --oneline |
| Search commit content (added/removed lines) | git log -S 'literal' --oneline or git log -G 'regex' --oneline |
| Who last touched each line | git blame path/to/file |
| Diff between two commits | git diff <a>..<b> -- path/to/file |
| Find when a symbol was introduced | git log --diff-filter=A -S 'symbol_name' -- path/ |
| List PRs that touched a file | gh pr list --state all --search 'path/to/file in:title,body' |
| Show a PR | gh pr view <number> |
| Show an issue | gh issue view <number> |
git log --oneline -n 20 -- <path>
is faster than reading individual commits.git log -S 'string' finds commits where the count of a literal
changed; -G 'regex' matches the actual diff. Use -S for adding/
removing a known identifier, -G for richer patterns.gh search prs/issues is broader than gh pr list --search; use it
when you do not have the file path handy.git log @{u}..HEAD shows commits on the current
branch that have not been pushed yet.