Test Plugin Installation / Validate skill content (push) Has been cancelled
Test Plugin Installation / Validate command parity and description sync (push) Has been cancelled
Test Plugin Installation / Validate plugin structure (push) Has been cancelled
Test Plugin Installation / Test plugin installation (push) Has been cancelled
Per review feedback: clarify that cherry-picking individual skills works,
but running two frameworks as active routers at once causes command-name
conflicts, competing routing, and clashing TDD philosophies. Recommend
one primary router + à la carte borrowing.
Resolve README.md Reference Checklists table conflict by keeping both new
rows: observability-checklist (this PR) and orchestration-patterns (#290,
already on main).
The Stop-the-Line Rule and Triage Checklist each have exactly 6 steps
(1-6). "Steps 4-10" referenced steps that never existed — this was an
original error present since the file's first commit, not a leftover
from a previous 10-step structure. Correct the range to match the
actual 6-step content.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The references/ directory ships five files, but the Reference Checklists
table in the README listed only four — orchestration-patterns.md was
missing. It is a real reference (linked from AGENTS.md and the agents
docs as the full pattern catalog), so add it to the table for parity
with the other four entries.
Every other shell script in the repo is 100755 (all six hooks/*.sh),
but skills/idea-refine/scripts/idea-refine.sh was committed 100644.
It has a #!/bin/bash shebang and is invoked as a runnable helper from
its SKILL.md. AGENTS.md also documents scripts/ as 'Required:
executable scripts'. Set the exec bit for consistency.
The validate-skills job pinned actions/checkout@v4 while the other two
jobs in the same workflow (test-fresh-install, test-plugin-structure)
use @v6. Align all three on @v6 for consistency.
The antigravity code-simplify command instructed the agent to read
"CLAUDE.md or AGENTS.md", but per docs/antigravity-setup.md the
Antigravity CLI reads AGENTS.md for project conventions. The CLAUDE.md
reference is a leftover from the Claude command variant. Align it with
the other platform commands, where each reads its own conventions file
(.claude reads CLAUDE.md, .gemini reads GEMINI.md).
The slash-command reference table in docs/getting-started.md lists every
lifecycle command except /code-simplify, even though it is documented in
the README, has command files for all platforms (.claude/.gemini/commands),
and the table already includes the more specialized /webperf. Add the
missing row mapping /code-simplify to the code-simplification skill.
hooks/simplify-ignore-test.sh was committed with mode 100644 while its
sibling test script hooks/session-start-test.sh is 100755. Both share
the same #!/bin/bash shebang and live in the same directory; set the
exec bit for consistency.
- Support single-quoted TOML description strings (previously silently returned null)
- Wrap file reads in try/catch to produce actionable CI errors instead of raw stack traces
- Remove dead tomlStems variable; declare allTomlStems once and compute allCanonicalStems for an accurate command count in the summary
- Simplify description mismatch output to always show all three values, removing a redundant conditional branch
When users manually copy hooks to .claude/ instead of installing via plugin, ${CLAUDE_PLUGIN_ROOT} is not set and the SessionStart hook silently fails.
This adds a fallback to ${CLAUDE_PROJECT_DIR}/.claude/hooks/ so the hook works in both plugin and manual install modes. If neither path exists, it silently succeeds.
Tools that scan agents/*.md as custom agent definitions (e.g. GitHub Copilot CLI) parse every Markdown file in agents/ and require YAML frontmatter. agents/README.md was docs, not an agent, so it triggered "malformed custom agent" warnings on every session start.
Moving the docs to docs/agents.md keeps agents/ containing only real agent definitions. Updates internal links in the moved file, in the four persona files, AGENTS.md, and adds a pointer from the root README.
Fixes#258
The recommended config attached the agent to the user's running Chrome
via --autoConnect ('recommended for most users'), giving it every open
window of the default profile: logged-in email, banking, GitHub
sessions. Combined with a page containing injected instructions, the
agent effectively holds the user's authenticated browser. The skill's
own Security Boundaries section treats browser content as untrusted,
but profile isolation is the layer that bounds the damage when those
rules fail.
Changes:
- Recommended config now uses --isolated (temporary profile, wiped on
close); documents that the server's default is already a dedicated
profile separate from the user's browser
- --autoConnect described accurately (Chrome 144+, requires enabling
remote debugging) and demoted to the logged-in-state use case
- New 'Profile Isolation' subsection in Security Boundaries with
escalation rules: dedicated profile -> test-only profile -> real
profile only with unrelated tabs closed
- Red flag added for attaching to the daily profile for localhost tests
Follow-up suggested in #223 review: folds in the useful half of #61
(the observability checklist) as this skill's quick-reference
companion, mirroring the security-and-hardening / security-checklist
pairing.
Aligned with the merged skill's framing: on-call questions first,
RED/USE metrics, cardinality rules, symptom-based alerting with the
page/ticket two-severity rule, telemetry verification, and a
pre-launch gate. Linked from the skill's Verification section and
registered in the README references table and CLAUDE.md.
Test Plugin Installation / Validate skill content (push) Has been cancelled
Test Plugin Installation / Validate plugin structure (push) Has been cancelled
Test Plugin Installation / Test plugin installation (push) Has been cancelled
The .claude-plugin/plugin.json agents array still listed only 3 personas;
add web-performance-auditor so the manifest matches the agents/ directory
(now 4). Verified with `claude plugin validate .`.
- README: remove "(Recommended)" from the Antigravity CLI install section
(Claude Code already carries that badge); bump the commands/ count to 8.
- Add commands/webperf.toml so Antigravity users get the /webperf
web-performance-auditor command at parity with Claude and Gemini.
Follow-up after the #222 merge left the new persona/command only half-wired:
- Register web-performance-auditor in the README agents table, the
getting-started "Using Agents" table, and CLAUDE.md (3 -> 4 personas).
- Document /webperf in CLAUDE.md and the getting-started command table.
- Add .gemini/commands/webperf.toml so Gemini users get /webperf too
(mirrors the Claude command; persona invoked inline rather than spawned).
Addy's review on #222: leading with "Invoke the agent-skills:performance-optimization skill" risks the auditor persona drifting into fixing code instead of auditing, which breaks the reviewer-vs-implementer line. The persona already delegates to skills/performance-optimization/SKILL.md from its Rules (step 9), so nothing is lost by letting the command spawn the persona directly.
Rename Core Process to Process, and move observability next to
implementation in the lifecycle sequence so it no longer contradicts
the skill's own instrument-as-you-build rule.
Fills the gap between debugging-and-error-recovery (dev-time) and
shipping-and-launch (launch-day monitoring): how to instrument code
as it's built so production behavior is visible and diagnosable.
Covers structured logging with correlation IDs, RED/USE metrics with
cardinality guidance, OpenTelemetry tracing, and symptom-based
alerting with runbooks. Follows the standard skill anatomy (Overview,
When to Use, Process, Rationalizations, Red Flags, Verification).
Registered in README tables/structure, CLAUDE.md phases, and the
using-agent-skills discovery tree (hooks/session-start-test.sh passes).
Package name was wrong (@anthropic/chrome-devtools-mcp does not exist).
Adds -y to skip npx confirmation prompt and --autoConnect as the
recommended default to connect automatically to a running Chrome instance.
Addy Osmani