Files
awesome-copilot/skills
Furkan Reha f32d7c320d fix(skills): anchor citations on the named line, and treat repo text as evidence (#2976)
Ports four corrections these two skills received upstream after a second trial
run against a real repository. #2951 merged the snapshot taken before them. The
bundled scripts are already identical to their upstream versions and are not
touched here.

1. Neither skill told the agent that text read out of the audited repository is
   data rather than instruction. These skills exist to read untrusted
   repositories, so a README, a code comment, a commit message or a dependency
   manifest reached the model with no framing -- and a line claiming a file is
   approved, or telling the audit to skip a module, reads exactly like a
   guardrail. Both skills now carry the rule and report such text as a finding
   instead of following it.

2. The citation rule allowed anchors to land beside the symbol rather than on
   it: the blank line above a definition, a decorator, or a line inside a
   multi-line literal. In one trialled file every anchor sat two lines above the
   def it named. The rule is now a single applicable test -- the line you cite
   must literally contain the thing you name, and a cited range must contain it
   on the first line. Quoted text is cited at the line the quoted characters are
   on, because a comment has its own line number and it is usually not the line
   of the code beside it.

3. "Never restate a count without the raw output in front of you" was ignored
   twice in that trial, so the rule flips from prohibition to requirement: any
   number stated must appear under Checks Run next to the command that produced
   it. Unwilling to show the command means describing the pattern rather than
   counting it.

4. Both Related Skills sections said the skill is one of seven and that the
   other five cover the remaining ground. Six, not five. Each section now names
   its sibling in this repository and links the remaining five out.

Front matter is unchanged, so the generated README tables do not move.
2026-09-08 09:48:27 +10:00
..
2026-03-05 21:53:41 +11:00
2026-04-28 11:29:28 +10:00
2026-06-18 11:28:03 +10:00
2026-04-20 12:31:29 +10:00
2026-02-16 22:43:41 +01:00
2026-08-05 15:43:58 +10:00
2026-06-16 11:18:02 +10:00
2026-06-15 10:55:29 +10:00
2026-01-06 21:35:41 +01:00
2026-03-16 10:27:54 +11:00
2026-06-16 11:50:25 +10:00
2026-05-15 11:06:16 +10:00
2026-07-17 10:37:35 -07:00
2026-03-13 13:45:17 +11:00
2026-07-23 10:50:25 -07:00