// Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.
Interact with the running VSCode extension via Playwright. Use when automating, testing, or debugging the OpenCode webview UI.
Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.
Implement a single phase of a spec. Use when given a spec file and a phase number to implement.
Browser automation CLI using Playwright. Use when automating browser workflows, filling forms, clicking elements, scraping pages, or debugging web issues.
Review a spec for under-specified areas, bugs, and adherence to the generate-spec skill. Use when asked to review, critique, or check a spec.
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
| name | update-docs |
| description | Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development. |
Update AGENTS.md files based on what was learned in this session about: $TOPIC
Read docs/updating-agents-docs.md for full guidelines before proceeding.
Review the conversation for learnings about the specified topic:
Determine where each learning belongs (lowest common ancestor):
AGENTS.md for repo-wide patternsdocs/*.md for detailed explanationsCheck if the target AGENTS.md already has related content:
Apply changes following the writing style in the guidelines
List what was updated and why