167 件（obra のリポジトリ） ・ 人気順
概要と使いどころ
Use when auditing a codebase for semantic duplication - functions that do the same thing but have different names or implementations. Especially useful for LLM-generated codebases where new functions are often created rather than reusing existing ones.
日本語の概要は準備中です。原文の説明を表示しています。
Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.
日本語の概要は準備中です。原文の説明を表示しています。
Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to run interactive CLI tools (vim, git rebase -i, Python REPL, etc.) that require real-time input/output - provides tmux-based approach for controlling interactive sessions through detached sessions and send-keys
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool
日本語の概要は準備中です。原文の説明を表示しています。
Use when demonstrating plugin workflow features - shows how skills can guide multi-step processes
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Claude Code CLI, plugins, hooks, MCP servers, skills, configuration, or any Claude Code feature - provides comprehensive official documentation for all aspects of Claude Code
日本語の概要は準備中です。原文の説明を表示しています。
Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle
日本語の概要は準備中です。原文の説明を表示しています。
Add a comment to a roborev code review and close it
日本語の概要は準備中です。原文の説明を表示しています。
Use MCP servers on-demand via the mcp CLI tool - discover tools, resources, and prompts without polluting context with pre-loaded MCP integrations
日本語の概要は準備中です。原文の説明を表示しています。
Create, manage, or connect to a headless Windows 11 VM running in Docker with SSH access. Use when the user wants to spin up, stop, restart, or SSH into a Windows VM.
日本語の概要は準備中です。原文の説明を表示しています。
Request a code review for all commits on the current branch and present the results
日本語の概要は準備中です。原文の説明を表示しています。
Iterative review-fix loop for the current branch — reviews via daemon, fixes inline, re-reviews until passing or max iterations reached
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to fix open failing reviews, invokes /roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or close reviews
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to fix open failing reviews, invokes $roborev-fix, or provides job IDs; do not use when the user only pastes review findings with no request to discover or close reviews
日本語の概要は準備中です。原文の説明を表示しています。
Request a design review for a commit and present the results
日本語の概要は準備中です。原文の説明を表示しています。
Request a code review for a commit and present the results
日本語の概要は準備中です。原文の説明を表示しています。
Use when reading or writing files in an Obsidian vault that is synced with obsync. Ensures changes are pulled before reading and pushed after writing. Also covers sync status, file history, version restore, and diagnosing sync issues.
日本語の概要は準備中です。原文の説明を表示しています。
Use when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding or enforcing project terminology, deciding where a new doc should live, or a routine re-audit of previously verified docs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly built instance with falsifiable assertions. Trigger on "test it end to end", "prove the UI actually works", "write/run a scenario", or after a change touches a user-facing surface that unit tests can't fully cover. Not for unit tests, pure code review, or API-only checks.
日本語の概要は準備中です。原文の説明を表示しています。
Request a design review for all commits on the current branch and present the results
日本語の概要は準備中です。原文の説明を表示しています。
Allows you to view the user's screen as well as several hours of history. Use when the user makes a reference to their recent work, for which it'd be helpful to see the screen. This skill MUST be used whenever you need to resolve ambiguity in a user request, where the user hasn't specified enough context to do the task. Examples include disambiguating the specific user/app/document/error the user is referring to. You must also use this skill if the user asks about any question regarding Chronicle or asks what you can see from the screen.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to prove, disprove, investigate, or find evidence for a claim about people, concepts, ideas, or their relationships. Also use when asked to explore connections, find who influenced what, trace how ideas developed, or answer questions that require reasoning over multiple linked notes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when acting as a project manager that delegates tasks to other coding-agent sessions (Claude Code, Codex, or Pi) - launch workers, assign them work, monitor progress, review their tool calls, and collect results
日本語の概要は準備中です。原文の説明を表示しています。