chadtmiller.com/knotless
git that lives in your Atmosphere account
1
10
Pull bodies open short and fold the full write-up in <details>
.knotless/pull.md+12−0
| @@ -10,6 +10,16 @@ | ||
not in `code`: its page shows it as a link with its title, and an | ||
issue named so lists this pull on its own page. --> | ||
| ||
<!-- Opener: the shortest text that tells a reader what this is for | ||
and whether it needs their attention, two or three sentences at | ||
most, and a picture where one shows it best: a person's words, or | ||
ones they approved. The rest folds below, under the model and | ||
effort that wrote it ("Claude Opus 5.5 · high"), or the author's | ||
name when a person did; keep the blank line after </summary>. --> | ||
| ||
<details> | ||
<summary>Model · effort</summary> | ||
| ||
## What changes | ||
| ||
<!-- What someone using knotless, or reading the code, finds different. | ||
| @@ -35,3 +45,5 @@ | ||
| ||
<!-- Optional: the kind of review wanted (a quick look, the design, | ||
one risky part) and where to start reading. --> | ||
| ||
</details> | ||
docs/guide/collaborating.md+7−0
| @@ -271,6 +271,13 @@ notes copied into it, so a section with nothing to say can be left out. | ||
The MCP `pull_template` and `issue_template` tools give the same, and `pull_create` and `issue_create` | ||
say to read it first. | ||
| ||
A template can ask for a short opener and fold its sections below it in | ||
`<details>`, which the pages and the iOS app draw closed under what its | ||
`<summary>` says, as GitHub does. The headings count inside a fold too. | ||
knotless's own `.knotless/pull.md` does this, so the full write-up an | ||
agent gives sits under its model's name, below what a person chose to | ||
say. | ||
| ||
## Label pulls and issues | ||
| ||
The owner defines the labels; then the owner and collaborators put them on. | ||
AGENTS.md+5−1
| @@ -244,7 +244,11 @@ named for it (`web/mermaid`, `serve/jetstream`), then `knotless pull create | ||
knotless://chadtmiller.com/knotless main knotless://chadtmiller.com/knotless | ||
<branch> "<title>" -m - < body.md`, the title and body written from | ||
`.knotless/pull.md` (`knotless pull template <repo>`); `-m -` keeps the | ||
shell off the Markdown. It is merged into `main` and deployed from there. A body saying `Fixes <issue>` (or Closes, Resolves), the issue by | ||
shell off the Markdown. The body opens with a short paragraph a person | ||
would write, what the pull is for and whether it needs a reader's | ||
attention, and folds the full write-up below it in `<details>`, under a | ||
`<summary>` naming the model and effort that wrote it, as the template | ||
lays out. It is merged into `main` and deployed from there. A body saying `Fixes <issue>` (or Closes, Resolves), the issue by | ||
its knotless.dev page or `at://` URI, closes that issue as it merges. Once its own checks pass, land it with `knotless pull merge <repo> | ||
<pull uri> --queue`, which returns at once: the runner lands queued | ||
pulls in batches, main with each squashed onto it as a commit of its | ||