Add repo-backend pointer skill (residual from agentic-os-kai#321) #30

New issue

Closed

opened 2026-06-04 10:45:20 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-06-04 10:45:20 +00:00

Owner

Problem

backend (coilyco-flight-deck/backend, generic python backend server) is the one
active repo from the agentic-os-kai#321 fan-out that never got its
repo-backend source-of-truth pointer skill.

History: a bare-name .agents/skills/backend/SKILL.md pointer was added to
agentic-os-kai (commit d375455), but it was dropped from agentic-os-kai's tree
by a later forgejo/main merge (f6c5d8b) and never re-created in the backend
repo. The sibling-repo migration that landed the other 16 repos
(agentic-os-kai#329 / commit cb2d3a2) did not include backend, so it is the
sole gap.

backend is in agentic-os-kai/scripts/repos-on-disk.txt and
data/repo-registry.md, so the architecture intends it to carry a pointer.

Proposal

Generate backend/.agents/skills/repo-backend/SKILL.md the standard way:

Ensure the Forgejo repo has a description + topics (coily exec sweep-repo-pointer-skills --phase metadata --only backend, or set them directly).
Run the generator: coily exec gen-repo-pointer-skill -- backend --from-json <forgejo-view.json> --repo-root <backend-checkout> (this is what scripts/sweep-repo-pointer-skills.py --phase generate automates).
Commit in the backend repo with a same-repo closes trailer, then push.

Note: scripts/sweep-repo-pointer-skills.py hardcodes ~/projects/coilysiren/
as the workspace, but backend lives in the coilyco-flight-deck org. Either
check backend out under the expected path or pass --workspace. Worth fixing
the hardcoded org assumption while here.

## Problem `backend` (`coilyco-flight-deck/backend`, generic python backend server) is the one active repo from the agentic-os-kai#321 fan-out that never got its `repo-backend` source-of-truth pointer skill. History: a bare-name `.agents/skills/backend/SKILL.md` pointer was added to agentic-os-kai (commit d375455), but it was dropped from agentic-os-kai's tree by a later `forgejo/main` merge (f6c5d8b) and never re-created in the backend repo. The sibling-repo migration that landed the other 16 repos (agentic-os-kai#329 / commit cb2d3a2) did not include backend, so it is the sole gap. `backend` is in `agentic-os-kai/scripts/repos-on-disk.txt` and `data/repo-registry.md`, so the architecture intends it to carry a pointer. ## Proposal Generate `backend/.agents/skills/repo-backend/SKILL.md` the standard way: 1. Ensure the Forgejo repo has a description + topics (`coily exec sweep-repo-pointer-skills --phase metadata --only backend`, or set them directly). 2. Run the generator: `coily exec gen-repo-pointer-skill -- backend --from-json <forgejo-view.json> --repo-root <backend-checkout>` (this is what `scripts/sweep-repo-pointer-skills.py --phase generate` automates). 3. Commit in the backend repo with a same-repo `closes` trailer, then push. Note: `scripts/sweep-repo-pointer-skills.py` hardcodes `~/projects/coilysiren/` as the workspace, but backend lives in the `coilyco-flight-deck` org. Either check backend out under the expected path or pass `--workspace`. Worth fixing the hardcoded org assumption while here. ## See also - agentic-os-kai#321 - parent fan-out, closed as superseded; backend was its lone residual. - agentic-os-kai#329 (commit cb2d3a2) - migrated the other 16 repos to `repo-<name>` source-of-truth. - agentic-os-kai#499 - the idempotent `sweep-repo-pointer-skills` helper.

coilysiren added the

label

2026-06-17 07:05:15 +00:00

coilysiren commented

2026-06-17 08:23:58 +00:00

Author

Owner

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.

coilysiren

2026-06-17 08:23:58 +00:00