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

How to find the symbols behind a bug question before editing with BGTS Context Engine

Ask a plain bug question and get the ranked code symbols that answer it.

Who it is forA developer or coding agent starting work on an unfamiliar repository, with a bug report that describes behaviour rather than file names.

The problemEmbedding search returns files that mention the words in the question, not the functions that set the behaviour and the callers that depend on it.

The outcomeA ranked, budgeted list of the symbols that participate in the behaviour, with a coverage report showing how much of the answer to trust.

What you need first

  • Docker with Docker Compose, to run PostgreSQL 16 with Apache AGE and pgvector
  • Python with pip
  • A local repository to index
  • A coding agent that can call MCP tools, or the bce command line

Steps

  1. docker compose -f deploy/docker-compose.yml up -d
  2. pip install bgts-context-engine
  3. cp .env.example .env
  4. bce migrate
  5. bce index --repo /path/to/your/repo --name my-service
  6. bce context --task "fix the login timeout in the meeting webhook"

Prompt for your agent

Using the bgts-context-engine repository, index the repository at <target repo path> with bce index, then run bce context with the bug description <bug description> as the task. Expected output: a ranked list of symbols with a coverage report. Verify that the top results include the function that sets the behaviour named in the bug.

Caveat. The benchmark figures in the README come from BGTS's own harness, which is not yet in this repository, so check the ranking on your own code before relying on it.

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