Eval: pf-design-token-check

[patternfly-jira-sync]

Write an eval.yaml for pf-design-token-check using agent-eval-harness.

Read the skill's SKILL.md. Identify what the skill uniquely teaches that the base model doesn't know without it. Write 2-3 test cases targeting those differentiators.

Each test case needs:

• A prompt (realistic user request)

• Fixture file(s) the prompt references

• Automated checks verifying expected output

Acceptance Criteria:

• eval.yaml exists at eval/pf-design-token-check/eval.yaml

• Contains 2-3 discriminating test cases

• All test cases pass locally via /eval-run

---

Jira Issue: PF-4378

[coderabbitai]

🔗 Related PRs

#29 - Add skill for writing unit tests for PatternFly ecosystem components [merged]
#108 - feat(skill): pf design token check skill [merged]
#115 - feat(PF-4273): add eval for pf-unit-test-generator skill [closed]
#131 - feat(PF-4363): add pf-assist agent and eval [merged]
#133 - feat(PF-4339,PF-4346,PF-4343): add scanner skill evals [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!