DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to map how a feature works across an unfamiliar repo with Agy Staff

Use agy's researcher persona to survey a topic in a codebase you do not know yet.

Who it is forA developer onboarding to a repo who needs a quick map of how one subsystem works.

The problemReading an unfamiliar codebase to answer one question costs a lot of time and context.

The outcomeA research report on the topic, returned when the job finishes.

What you need first

  • Antigravity CLI (agy) installed and authenticated
  • Node.js installed
  • Claude Code or OpenAI Codex (Pi and OpenCode are also supported per the README)

Steps

  1. Install the Antigravity CLI with curl -fsSL https://antigravity.google/cli/install.sh | bash, then confirm with agy --version.
  2. Install the plugin in Claude Code with claude plugin marketplace add keli-wen/agy-staff and claude plugin install agy@agy-staff, or in Codex with codex plugin marketplace add https://github.com/keli-wen/agy-staff and codex plugin add agy@agy-staff.
  3. Restart the harness.
  4. Run /agy:researcher how does auth work in this repo in Claude Code, or $agy:researcher how does auth work in this repo in Codex. (inferred, check the README)
  5. Wait for the report and follow up with a narrower question if needed.

Prompt for your agent

Using the keli-wen/agy-staff plugin, ask the researcher persona how <topic> works in <repo>. Expect a written report on that topic. Verify that the report cites specific files or functions it read.

Caveat. Researcher output is only as good as the files agy can read in your workspace, and the default run is unrestricted, so review what it reads and runs.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page