usage/status parsing
- Updating Claude OAuth/web endpoints or cookie import
- Adjusting Claude CLI PTY automation
- Reviewing local cost usage scanning
---
# Claude provider
Claude supports three usage data paths plus local cost
Trigger Claude review by commenting `@claude review` on the PR.
3. Address every review comment (`gemini-code-assist`, `coderabbitai`, `claude[bot]`): fix, push, reply on the thread (`Addressed
again until you get it.
4. Implement the tests first. Ask for confirmation and codereview.
5. Once tests are approved, once again suggest your implementation plan for making them
Analysis Skill
## Project Overview
This repository contains **Claude SEO**, a Tier 4 Claude Code skill for comprehensive
SEO analysis across all industries. It follows the Agent Skills open standard
downstream.
- Every assertion must be capable of failing. An assertion about a condition the code
cannot produce is noise.
- Confirm the test actually runs in CI. Some test files
multiagent: { type: "coordinator", agents: [...] }` roster so the analyst hands its numbers to a toolless reviewer. The handoff events (`session.thread_created`, `agent.thread_message_sent/received`) already arrive on the stream; the reducer
first. Do not infer visual evidence from runtime readiness,
structural tests, inline previews, or codereview, and do not claim the visual gate passed.
**Scope of this gate.** It governs
endpoints, Playwright for UI |
| `verification` | before claiming "done" — run real commands, show evidence |
| `code-review` | reviewing a diff/PR — spec compliance then code quality |
| `java-checkstyle` | after touching `.java` — runs
names** before use
- **Keep CLAUDE.md updated** when adding new patterns or dependencies
- **Test your code** - No feature is complete without tests
- **Document your decisions** - Future developers (including yourself) will thank
idea to paper. Each skill provides expert-level guidance (200-500 lines) with real code examples, troubleshooting guides, and production-ready workflows.
**Mission**: Enable AI agents to autonomously conduct
write-file`/`kill`; JSON on stdout, `exec` streams remote output + propagates the remote exit code; secrets only via env/stdin, never argv — tests substitute the interpreter via `SANDBOX_E2B_PYTHON
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
distribution, category breakdown, or timeline as fits), and the reviewer note carried over. In Cowork this renders inline. In Claude Code I'll write an HTML file to [outputs folder
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.