Summary
One tool, one question, and the repository does not have to be yours.
ask_repo takes a repo, a prompt and optionally a ref, and that is the entire surface — there is nothing to configure and nothing else to call. The examples it ships with aim at understanding rather than change: how a server handles concurrent connections, how an API is meant to be used. Nothing here writes to a repository or opens a pull request, so the output is an answer you act on yourself.
What it is
A single-tool server that takes a repository, a question and an optional ref, and answers from the code it finds there.
What you get
- A question answered against a repository named as owner/name — nginx/nginx, hashicorp/terraform
- A ref accepted alongside the question, so the answer is read from that revision rather than whatever is current
- Architecture questions of the kind the tool's own examples put — how nginx handles concurrent connections, walking the event loop, worker process model and connection state transitions
- Integration questions put to a library's own source rather than to its documentation
Requirements
The owner and name of a Git repository you want to ask about, and the question to put to it — no account or key is set up for this server.
Setup effort
One command — npx -y instagit@latest