User asks to "browse a Qred repo", "search code across Qred repos", "list Qred repos", "find <term> in <repo>", "view PR/issue in <repo>", or "read a file from a Qred repo". Read-only: scoped to the Qred GitHub org; refuses mutating gh subcommands (merge, close, edit, delete, transfer, archive). Not for: code review (use /review); not for: DB exploration (use /backoffice-database).
Layered repository exploration and code searching across the Qred GitHub organization.
Read-only and informational operations only. Refuse any mutating gh subcommand (write, delete, close, merge, edit, transfer, archive) and explain why.
| Input | Intent | Approach |
|---|---|---|
(empty) or repos | List repositories | Direct |
prs <repo> or pr <repo> #<n> | List or view PRs | Direct |
issues <repo> or issue <repo> #<n> | List or view issues | Direct |
Starts with gh | Pass-through command | Direct |
Repo name (e.g., qred-mcp-proxy) | Orient to repo | Layered; enter at Layer 1 |
tree <repo> or <repo>/<path>/ | Navigate structure | Layered; enter at Layer 2 |
| Search term (no path separators) | Search code across org | Layered; enter at Layer 3 |
<term> in <repo> | Search code in repo | Layered; enter at Layer 3 |
<repo>/<file-path> | Read file contents | Layered; enter at Layer 4 |
gh repo list Qred --limit 30 --no-archived --json name,description,url,isArchived,pushedAtgh pr list / gh issue list with relevant --json fieldsgh pr view / gh issue view with relevant --json fieldsRun gh repo view Qred/<repo> to get README and metadata.
Run gh api repos/Qred/<repo>/contents/<path> to get directory listing and present as a tree.
gh search code --owner Qred "<term>" --limit 30 --json path,repository,textMatchesgh search code --repo Qred/<repo> "<term>" --limit 30 --json path,repository,textMatchesRun gh api repos/Qred/<repo>/contents/<path> to get file content.
300-line threshold: if a file exceeds 300 lines, show the first 100 lines and ask before showing more.