demo: skill-audit line-anchored comments#9
Conversation
- github actions workflow for eval runs on skill preview PRs - 2027.config.yaml extends skill-audit with org rules (mjs-only scripts) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Same semantic — still vague about the output artifact, so CONTENT-005 fires. Line 3 is in the PR diff, so the audit's review comment will anchor to the exact line rather than file-level fallback. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
caffeinum
force-pushed
the
demo/skill-audit-line-anchor
branch
from
f4d1cdc to
f718d5f
Compare
|
2027 auto-runs evals against preview deployments of your docs. To enable this, install one of:
Once a preview is deployed, open a new PR and we'll run the eval automatically. Evaluating agent experience using 2027.dev · View dashboard |
![2027-evals[bot]](https://avatars.githubusercontent.com/in/3339941?s=60&v=4){kind=small}
There was a problem hiding this comment.
🟡 check threw: You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.
There was a problem hiding this comment.
🔴 check threw: You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.
There was a problem hiding this comment.
🟡 check threw: You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.
There was a problem hiding this comment.
🟡 check threw: You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.
There was a problem hiding this comment.
🔴 check threw: You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.
|
closing — superseded by a fresh test PR for skill-audit v6 smoke |
2 participants
Demo PR for the queue's skill-audit cohost. Touches line 3 of
skills/autobrowse/SKILL.md(thedescriptionfield). Expected behavior: the audit posts an inline review comment anchored to line 3 (CONTENT-005 fires on that exact line, and line 3 is inside the diff hunk so GitHub accepts it).Replaces stale test PRs #3, #6, #7, #8 which are now closed.