Skip to content

Commit 6fda350

Browse files
manzoorwanijkclaude
andcommitted
Fix: Use relative paths in files_found output
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 1a0348c commit 6fda350

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

  • projects/github-actions/agent-experience-eval

projects/github-actions/agent-experience-eval/prompt.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ a JSON object matching this exact schema:
77
"version": 1,
88
"score": <number 0-100, the average score from the report>,
99
"grade": "<A|B|C|D|F, from the report>",
10-
"files_found": ["<paths to all AI instruction files found>"],
10+
"files_found": ["<relative paths from repo root, e.g. .claude/CLAUDE.md not /home/runner/work/repo/.claude/CLAUDE.md>"],
1111
"criteria": {
1212
"commands_workflows": { "score": <0-20>, "max": 20, "notes": "<feedback from report>" },
1313
"architecture_clarity": { "score": <0-20>, "max": 20, "notes": "<feedback from report>" },
@@ -26,4 +26,5 @@ IMPORTANT:
2626
- If no AI instruction files exist, score 0, grade F.
2727
- The "score" field must equal the sum of all criteria scores.
2828
- The "grade" must match the score: A (90-100), B (70-89), C (50-69), D (30-49), F (0-29).
29+
- All file paths in "files_found" must be relative to the repo root (no absolute paths).
2930
- Output ONLY the JSON object. No markdown code fences. No text before or after.

0 commit comments

Comments
 (0)