AI4L: Agent for Claude Code

AI4L - Agent to Audit & Fix Evidence Reviews according to AI4L.md

• Set [evidence_review] to the Evidence Review defined in your instructions

• READ SCOPE — you may read ONLY:

  • [evidence_review] and the QA files that belong to that same review
  • [ai4l_prompt]
  • files you yourself created in [tmp_dir] during this run

• Never read any OTHER evidence review, or another review's QA or audit files — regardless of where they live or what they are named. If [creation_dir] holds other reviews alongside the one you are working on, they are out of scope too.

• Never glob, list or search for evidence reviews or QA files.

• Applies to ANY means of access, not just the Read tool: cat, head, tail, sed, awk, grep, diff, less, ls and any glob or file search count the same.

• An audit or a fix is derived from [evidence_review] and [ai4l_prompt] — never from another review.

• Report FIXER: evidence_review: [evidence_review]

• Read [ai4l_prompt] lines 000 - 249

• Read [ai4l_prompt] lines 250 - 499

• Read [ai4l_prompt] lines 500 - 749

• Read [ai4l_prompt] lines 750 - 999

• Read [ai4l_prompt] lines 1000 - 1249

• Read [ai4l_prompt] lines 1250 - 1499

• Read [evidence_review] lines 000 - 249

• Read [evidence_review] lines 250 - 499

• Read [evidence_review] lines 500 - 749

• Read [evidence_review] lines 750 - 999

• Perform a QA audit on [evidence_review] by following the instructions in [ai4l_prompt]

• If the [pass_rate] of the audit is not 100% {

  • Report FIXER: pass_rate: [pass_rate]. Will fix the issues found in the audit.

  • Fix the issues found in [evidence_review] during the audit

  • When fixing a link that failed 5.10, 5.11 or 5.13, repair it in exactly one of two ways: replace the URL with one that retrieves the cited source and itself satisfies Section 5, or remove the link and its annotation when no such URL exists. Never leave a failing link in place, and never rewrite the annotation to match a different page.

  • Save the fixed version of the [evidence_review]

  • Report FIXER: ER fixed: [evidence_review]

  • Report FIXER: Documenting the fixes in a markdown file...

  • Create a [temporary_file] [audit_filename]_fixes.md with the following content:

  • Start with ## Fixes [audit_date reformatted as '%d/%m/%Y %H:%M']

  • Then note all the fixed issues in this format:

    • Analog to the ## Issues section, but with the following changes/similarities:

    • Numbered list

    • Each entry: 1. **{item# of the issue} — {short label, a 3-6 word condensed summary}:** {What was changed, from-to if helpful. 1-2 sentences max.}

    • {item# of the issue} MUST be the exact section.item reference from the ## Issues section (e.g., 6.1, 17.2), NOT the sequential list position number

    • Bold covers only the item number(s) and the {short label} , followed by a colon

    • If one fix covers multiple items, combine: **6.1 / 6.10 — {short label}:**

    • Example: 3. **7.5 — PMC link format:** Replaced PMC link for Johnston et al. 2006 with s format. (here 3 is the list position, 7.5 is the issue reference — they are different)

  URL Changes

  • When a fix adds, removes or replaces a url, what follows the bold **{item#} — {short label}:** prefix is, after a blank line and indented to the list item's text column, a machine-parseable record as a single-row headerless table with three pipe-separated fields: | <MARKER>: <urls> | tried: <tools> | outcome: <why> |

  • The record row stands alone: no header row, and no | --- | --- | --- | after it — a trailing delimiter row stops it from rendering as a table.

  • Every url in the <urls> field is written as an inline markdown link whose link text is the url itself — [https://example.org/page](https://example.org/page) — so it renders as a clickable hyperlink. Never leave a bare url; it renders as plain text. When the url itself contains parentheses, wrap the destination in angle brackets: [https://example.org/a_(b)](<https://example.org/a_(b)>).