Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/developer
Core developer rules and coding conventions for gh-aw changes.
Passed 21 of 22 test cases with the skill, and 5 of 22 without it.
and 22 more in the full report
17 fixed4 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
I modified several Go source files across the codebase. What is the single change-type command specified in the playbook for Go file formatting after editing?
| Checked | Without skill | With skill |
|---|---|---|
| specifies make fmt for Go file changes | Missed | Passed |
The instructions your model reads when the skill loads.
Use this reference for gh-aw technical specs and development guidelines across code organization, validation, security, and implementation patterns.
Use this section for the detailed day-to-day command flow that was intentionally removed from AGENTS.md to keep first-run ambient context small.
Run validation in tiers — catch compile errors early, defer slow tests to the final pass only.
make build && make fmt
report_progress call (fast, <30s — no tests)
make agent-report-progress-no-test
report_progress call (change-scoped, includes impacted Go tests)
make agent-report-progress
make agent-finish
Key rule: Run
test-unitonly before the finalreport_progresscall, not before intermediate saves. The pre-PR targets scope formatting, linting, tests, and workflow drift checks to the branch changes.
Timeout budget:
make agent-report-progressshould normally finish in under 30 seconds. Workflow source or compiler changes additionally run the full workflow drift check. SetTEST_UNIT_RUN_FULL=1only when the full Go suite is required.
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.