
F1 Test Drive
This runs end-to-end validation of the Cyrus agent system by spinning up an F1 server, creating test issues, starting agent sessions, and verifying that activities flow correctly from issue tracker through EdgeWorker to rendering. You'd reach for this before merging changes to core runner or harness code to catch integration breaks early. The protocol is methodical: setup a test repo, verify each component in sequence, optionally test the Slack chat path with synthetic events, then write up results in a structured markdown report. The pass/fail criteria are practical and the skill explicitly stays harness agnostic so both Claude subagents and other workflows can reference the same test protocol. It's manual QA codified into repeatable steps with clear exit conditions.
- skills.sh installs
- 134
- GitHub stars
- 615
- last updated
- Jun 3, 2026
Install
$ npx -y skills add ceedaragents/cyrus --skill f1-test-drive --agent claude-codeInstalls into .claude/skills of the current project.
Files
F1 Test Drive
Applicability (required before setup)
This is the canonical F1 applicability policy. Inspect the actual diff against the PR base and identify the behavior that needs validation before starting F1, selecting a fixture, or creating a report. Task size, issue labels, filenames, and a generic request to verify/ship are not sufficient reasons to run F1.
Sponsors
Details
- Repository
- github.com/ceedaragents/cyrus
- Category
- Testing & QA
- First seen
- Jun 3, 2026