write_repo_map
Creates and updates a shared GitHub repository map for developer and reviewer briefs, covering layout, entry points, build/test/lint commands, conventions, and known traps.
Instructions
Write the map of a GitHub repo (owner/name) that the builder and reviewer briefs serve:
layout, entry points, how to install, build, test and lint, conventions, the files tickets
touch most, known traps. One map per repo, shared by every project on it, at most 8,000
characters (about 2,000 tokens). body replaces the whole map, so start from the one in your
brief and pass its version as base (leave it empty when the repo has no map). If someone
wrote the map since, nothing is written and the answer is the map now: fold your change into it
and write again. note says what changed and becomes a dated line in its history. Write it when the
brief says the repo has none; update it when a merged PR changes the layout or the build, test
or lint commands.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"repo": "<repo>",
"body": "<body>",
"note": "<note>"
},
"name": "write_repo_map"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| base | No | ||
| body | Yes | ||
| note | Yes | ||
| repo | Yes | ||
| project | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |