plugins/kyberforge/skills/agent-author/SKILL.md

@@ -56,9 +56,8 @@ Before touching the filesystem, confirm you have:
 - [ ] Root directory (plugin root, project root, or `~` for user scope)
 - [ ] Agent purpose — one sentence describing the task this agent handles
 - [ ] Trigger condition — when should the runtime delegate to this agent?
-- [ ] Capture `git log --oneline -1` now, before touching the filesystem — Step 5 needs it to verify a real commit landed
 
-If any are missing, stop and ask before proceeding.
+If any are missing, stop and ask before proceeding. Then capture `git log --oneline -1` before touching the filesystem — Step 5 needs it to verify a real commit landed.
 
 Verify `kyberforge:agent-audit` is available — it ships with the kyberforge plugin and is co-installed with this skill. If unavailable, stop and tell the user to install the kyberforge plugin before continuing.
 
@@ -233,6 +232,8 @@ Before editing, state which root causes were identified, what evidence supports
 
 Edit any file the signals point to. Generalize the fix — find the underlying gap, not the specific example that failed. For every sentence you add, ask: "Would the agent get this wrong without it?" A shorter, focused definition consistently outperforms an exhaustive one. For Copilot files, verify no Claude Code-only fields are introduced.
 
+If the edit adds or removes research-sourced content, update `source_keys` in the edited file(s) and the corresponding entry in `sources.md` per Create flow's Step 4.
+
 ### Step 5 — Validate and close
 
 Re-run the validation checklist from the create flow's Step 5 on any edited file.