coilyco-flight-deck/backend
2
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Add repo-pointer skill: move source-of-truth from agentic-os-kai #19

New issue
Closed
opened 2026-05-27 09:10:04 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-05-27 09:10:04 +00:00
Owner
Copy link

Problem

Per agentic-os-kai#321, the repo-pointer skill for this repo currently lives at agentic-os-kai/.agents/skills/<repo>/SKILL.md (wrong source-of-truth address). It should live in this repo as the canonical copy, with agentic-os-kai symlinking it in.

Proposal

  1. Create .agents/skills/<repo>/SKILL.md mirroring the body at agentic-os-kai/.agents/skills/<repo>/SKILL.md, with relative paths rewritten from ../../../../<repo>/ to ../../../ (since the pointer now lives one level deeper inside the target repo).
  2. If .agents/skills/categories.yaml exists in this repo, add a kind: exact entry for the repo (or kind: repo if the pre-commit pin is v0.5.0+). Most likely no categories.yaml exists - in that case skip.
  3. Commit with closes #N.
  4. In agentic-os-kai: delete the local SKILL.md, run ./setup.sh so the new symlink lands (relink_repo_pointers step), update the categories.yaml entry for the repo to add role: external-symlink, commit (use git pull --rebase first to avoid racing with sibling fanout dispatches).

See also

  • agentic-os-kai#321 - fanout tracker.
  • agentic-os-kai#319 - pattern landed for the first 3 repos.
## Problem Per [agentic-os-kai#321](https://forgejo.coilysiren.me/coilysiren/agentic-os-kai/issues/321), the repo-pointer skill for this repo currently lives at `agentic-os-kai/.agents/skills/<repo>/SKILL.md` (wrong source-of-truth address). It should live in this repo as the canonical copy, with agentic-os-kai symlinking it in. ## Proposal 1. Create `.agents/skills/<repo>/SKILL.md` mirroring the body at `agentic-os-kai/.agents/skills/<repo>/SKILL.md`, with relative paths rewritten from `../../../../<repo>/` to `../../../` (since the pointer now lives one level deeper inside the target repo). 2. If `.agents/skills/categories.yaml` exists in this repo, add a `kind: exact` entry for the repo (or `kind: repo` if the pre-commit pin is v0.5.0+). Most likely no categories.yaml exists - in that case skip. 3. Commit with `closes #N`. 4. In agentic-os-kai: delete the local SKILL.md, run `./setup.sh` so the new symlink lands (relink_repo_pointers step), update the categories.yaml entry for the repo to add `role: external-symlink`, commit (use `git pull --rebase` first to avoid racing with sibling fanout dispatches). ## See also - agentic-os-kai#321 - fanout tracker. - agentic-os-kai#319 - pattern landed for the first 3 repos.
coilysiren commented 2026-06-17 08:23:58 +00:00
Author
Owner
Copy link

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:59 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-36
ward-salvage/backend-2a750c77
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/backend#19
No description provided.