SeeRepo with GitHub Copilot

GitHub Copilot's coding agent takes a task, works on a branch and opens a pull request. SeeRepo shows you what it changed and how it connects.

The signature it leaves

Copilot authors its commits and the person who gave it the task is the co-author. It can only push to a branch that starts with copilot/, or to the pull request it was asked to work on (Copilot coding agent). Each commit also carries an Agent-Logs-Url line with its session (GitHub changelog).

How SeeRepo recognizes it

A commit counts as Copilot's when its author or its Co-Authored-By line says "copilot". A merge of a branch that starts with copilot/ also counts.

Where it shows in SeeRepo

• Made by, on a part's sheet: its logo next to the people. Click it and the map shows only what GitHub Copilot touched.
• Journey: its posts tell, day by day, what it did, with its mark; Who wrote it, on the wall, what share it signed since the start. Tap it there to open its sheet: what it fixed, what it left and which modules it worked on this month, with the link to its posts. See Journey.
• Moments: the day it starts writing most of the project, the moment "GitHub Copilot took over from …" stays.
• The filter: under Agent, pick GitHub Copilot to see only its work.

The full list of agents SeeRepo recognizes is in the Agent directory.

Hand it a prompt from SeeRepo

SeeRepo writes prompts for what's worth fixing, ready for GitHub Copilot:

1. Open Health and tap a task: failing tests, errors in production, packages with security flaws, files nothing uses… Its sheet opens. See Health.
2. Click "Copy prompt". The prompt names your repo, lists the files, and says what to do.
3. Paste it into GitHub Copilot: it will know which files to read.

If your project has no automatic tests, Health says so in Tests ("They don't run on their own") and offers "Copy prompt to make them run on their own": GitHub Copilot can set them up in a few minutes.