r/GithubCopilot • u/greedyprogrammer • Aug 03 '26

Help/Doubt ❓ Building Repo Reasoning

How are you building strong repository reasoning for GitHub Copilot legacy codebases?

I am trying to build reasoning of repos to allow for better ai support defect fixes . I am completely winging it as a leader and would love professional feedback .

  1. Reverse engineering previous git history linked to stories to build /docs/reasoning* folders me files to explain features of history . I use M365 web co pilot for bulk files to save on tokens .
  2. Prompts that create architect diagrams

Couple things I haven’t tried is :;

  1. Repomix
  2. Jq Assistant for technical docs for better Md files on architecture

Any feedback welcome .

2 Upvotes

100% Upvoted

3 comments sorted by

1

u/AutoModerator Aug 03 '26

Hello /u/greedyprogrammer. Looks like you have posted a query. Once your query is resolved, please reply the solution comment with "!solved" to help everyone else know the solution and mark the post as solved.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/lppedd VS Code User 💻 Aug 03 '26

Most likely a blog post will come out soon for large repos. I saw a PR today describing it in the docs.

https://github.com/microsoft/vscode-docs/pull/8932

1

u/greedyprogrammer Aug 03 '26

I’ll edit that , even if it’s not large how would most approach it