From 19c83d685dd8cf2fbcf3e0847bd59fdbcb5cac69 Mon Sep 17 00:00:00 2001 From: Aaqibhafeez Khan Date: Thu, 22 Oct 2026 18:35:58 +0530 Subject: [PATCH] fix: address verification artifact review feedback Keep the approved skill guidance and defer the sample regeneration to the maintainer rather than presenting a hand-edited page as generated output. Signed-off-by: Aaqibhafeezkhan <292322256+Aaqibhafeezkhan@users.noreply.github.com> --- skills/explain-diff-html/SKILL.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/skills/explain-diff-html/SKILL.md b/skills/explain-diff-html/SKILL.md index 71d0a72..0547709 100644 --- a/skills/explain-diff-html/SKILL.md +++ b/skills/explain-diff-html/SKILL.md @@ -359,6 +359,20 @@ A sparse pull request body leaves the Background section with no why. When no record supplies one, say what the change does and what it enables, and do not invent a motivation the record does not support. +When the page says a fact cannot be verified, name the public artifact that +would let a reader check it: the pull request number and URL, branch name, commit +SHA, or other concrete ref. Do not leave phrases such as "the earlier pull +request" or "another branch" unanchored when the source record identifies them. +Link those artifacts when the host supports it. When an artifact exists only on +a personal fork, link the upstream pull request that carries it and write the +SHA or branch name as plain text rather than a fork URL. This rule identifies +public objects, not people. + +Do not name individual contributors on the page, and do not publish unresolved +claims about whether someone was credited correctly. If attribution is not +necessary to explain the code change, omit the attribution discussion entirely +rather than investigating or repeating it. + Delegate broad reads to read-only sub-agents so the main context stays lean. A sub-agent returns only its summary, so ask for the conclusions and the `file:line` anchors you will need later, not for pasted file contents.