Skip to content

docs(bench): add pr-agent-bench skill (how-to-read runbook)#218

Open
hfurkanbozkurt wants to merge 10 commits into
bench/harness-integrityfrom
bench/pr-agent-bench-skill
Open

docs(bench): add pr-agent-bench skill (how-to-read runbook)#218
hfurkanbozkurt wants to merge 10 commits into
bench/harness-integrityfrom
bench/pr-agent-bench-skill

Conversation

@hfurkanbozkurt

@hfurkanbozkurt hfurkanbozkurt commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

PR 3 of 3 — split of #194. Stacked on PR 2 (base branch bench/harness-integrity).

Concern: docs only. Adds .agents/skills/pr-agent-bench/SKILL.md — a passive skill / runbook for reading and interpreting an aws-blocks PR agent-bench run: what the report's columns, colored balls (🟢 ⚪ 🟡 🔴), Judge dimensions (F/S/P/C/B), composite/Score, and stop_reason values mean, plus a 60-second regression-triage runbook.

Single commit ab85029; the diff touches only that one new file (+187). No code, no published @aws-blocks/* package changes.

Base: bench/harness-integrity (PR 2).

Stack (bottom → top): #216#217#218 · supersedes #194.
Supersedes #194.

H. Furkan Bozkurt added 2 commits July 17, 2026 20:49
…or slug

- trace caveat: only an ungraceful GitHub SIGKILL (hard timeout-minutes:35 kill before the graceful flush) writes no trace.json; the internal-deadline path (BENCH_AGENT_DEADLINE_SEC, stop_reason wall_clock_timeout) now flushes a message-only trace, so timed-out cells stay analyzable; genuinely trace-less => stop_reason is the answer (infra -> re-run)
- fix intra-doc anchor: change em-dash to colon in the 'Reference:' header so its GitHub slug is single-hyphen, matching the existing [reference](#reference-what-the-current-v1-report-contains) link
@changeset-bot

changeset-bot Bot commented Jul 17, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: e28e51e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

H. Furkan Bozkurt added 3 commits July 17, 2026 23:39
…er are counted (INCLUDED), only harness_error is excluded

Step 2 previously bucketed dead_server, wall_clock_timeout, max_tokens and agent_timeout as 'infra/harness noise -> NOT a PR signal -> re-run', contradicting scoring.mjs (isCountedFailKlass: agent_fail + dead_server are INCLUDED as composite 0) and the SKILL's own Reference section. Rewrote the triage table into 3 classes matching scoring.mjs exactly: harness_error (EXCLUDED, re-run/not a PR signal), agent_fail + dead_server (INCLUDED composite-0 counted failures that moved the mean; re-run only to disambiguate transient-vs-real), scored (INCLUDED, graded). Added a 'trap to avoid' note and corrected the worked-example cognito bullet to call the max_tokens 0 a counted agent_fail, not excluded noise.
…/B live in judge artifact JSON, not the row
@hfurkanbozkurt
hfurkanbozkurt marked this pull request as ready for review July 19, 2026 20:35
@hfurkanbozkurt
hfurkanbozkurt requested a review from a team as a code owner July 19, 2026 20:35
H. Furkan Bozkurt added 3 commits July 20, 2026 05:30
…nt-bench-skill

Brings in the #216 review-nit doc fixes (via the harness-integrity
forward-merge). Additive merge; no history rewrite.
dev_server_dead sat under a column headed 'Signal (stop_reason / status)'
but it is a klass_reason, not a stop_reason. Broaden the heading to
'stop_reason / klass_reason / status' so the dead_server cell is labeled
accurately, consistent with the Reference section's stop_reason enumeration
(which correctly omits dev_server_dead).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant