og

Plugin og from marketplace duplico in duplico/claude-og-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (8)

• check-wsl

  Run the og-check-wsl diagnostic: probe the WSL2/Windows interop surface (notify-send, WSLg, PowerShell, BurntToast, cmd.exe, clip.exe, sshd) and report which path the plugin's notify hook will use. Pass --test-notify to actually fire a desktop toast.

• closed-loop-helpers

  Closed-loop PR review protocol and helper scripts. Preloaded by the closed-loop-runner agent.

• copilot-reviews

  How to trigger and correctly find GitHub Copilot code reviews on a PR. Opt-in -- load only when the user brings Copilot into the review cycle.

• orchestrate-init

  Bootstrap a repository's Claude Code setup: investigate the stack, then generate a project orchestrator overlay, CLAUDE.md, permissions, optional domain agents, and gitignore entries. Run once per repo to get from zero to a useful, familiar orchestration setup.

• orchestrate

  Become the orchestrator for the current repository: scan repo + available subagents, check GitHub state, then coordinate and delegate work. Use when the user wants to coordinate multi-step or multi-repo work, dispatch subagents, run a review/fix loop, or asks to 'orchestrate' / 'coordinate' a task.

• pr-response-protocol

  Protocol for responding to PR review comments. Preloaded by developer agents.

• refresh

  Reconcile an existing repo's og setup with the current plugin: check plugin freshness, find duplicated generics, migrate legacy numbered rules to the namespaced scheme, lint for anti-patterns, and fact-check the overlay against the actual repo. Report-first; nothing changes without confirmation.

• sync

  Apply plugin updates down into this project's .claude/ overlay and agents. Fixes bare references to plugin agents/skills that should be og:-prefixed, and inserts shared-utility rows missing from the overlay's agent table. Run after a plugin update or whenever the project files have drifted from the

Subagents (7)

• closed-loop-runner

  Runs a closed-loop session for an issue or PR. Handles the full lifecycle: PR creation, CI monitoring, review polling, and review-fix cycles until completion or escalation. Repo- and stack-agnostic.\n\nExamples:\n\n<example>\nContext: Orchestrator dispatching for an issue (no PR yet).\nassistant: \"

• editor

  Use this agent to verify formatting, linting, or style compliance for any code, configuration, or documentation. This includes: reviewing code for style consistency before committing, resolving questions about proper formatting in a specific context, evaluating whether existing lint rule exclusions

• just-expert

  Use this agent when working with justfiles, creating new recipes, refactoring existing just configurations, or when questions arise about just syntax and best practices. This agent should be used proactively whenever justfile modifications are being made or when organizing build/task automation. Exa

• orchestrator-developer

  Use this agent to implement features, fix bugs, or address issues/PR comments in any repository. It creates an isolated git worktree, works independently, commits incrementally, and opens or updates a PR. Stack-agnostic: detects the project's build/test tooling. Preloads the PR response protocol.\n\

• orchestrator-reviewer

  Use this agent for adversarial code review before commit or merge, convention-adherence checks, and triage of incoming PR review comments. Provides fresh, skeptical eyes and verifies the issue→PR→code chain. Stack-agnostic.\n\nExamples:\n\n<example>\nContext: Changes are ready for review before comm

• orchestrator-tester

  Use this agent to write tests, run the project's test suite, investigate flaky or failing tests, and validate behavior end-to-end. Stack-agnostic: detects the test runner and conventions. Use it to add coverage for a new feature or to diagnose a CI failure.\n\nExamples:\n\n<example>\nContext: A new

• web-doc-searcher

  Use this agent to look up documentation for tools, libraries, or APIs that may be newer than your knowledge cutoff or are less commonly documented. Use it when you encounter an unfamiliar tool, need to verify current syntax/behavior, or when the user explicitly asks about documentation for an extern

Hooks (5)

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/git_branch_guard.py

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/github_disclosure.py

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/worktree_cleanup_guard.py

• PreToolUse

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/worktree_guard.py

• Notification

  python3 ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/notify_wsl.py

Similar plugins