ワンクリックでManusで任意のスキルを実行

gco

スター10

フォーク2

更新日2026年6月8日 04:01

Run GitHub Copilot CLI as a read-only sub-agent from Claude Code. Use when: (1) User says 'gco', 'copilot', or 'ask copilot', (2) Delegating code review or research to Copilot, (3) Getting a second opinion on code or architecture. Read-only mode (no file writes), gpt-5.4 model.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Takazudo

Takazudo/claude-resources

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

GitHub Copilot Read-Only Sub-Agent

Run GitHub Copilot CLI in read-only mode for code review, research, and investigation tasks.

How It Works

Copilot runs non-interactively with -p (prompt) and -s (silent output)
Read-only enforced via --deny-tool='write' (hard tool-level block) and read-only preamble in prompt
Uses --no-ask-user and --allow-all-tools for fully autonomous execution
Model: gpt-5.4
Timeout: 15 minutes

Process

Step 1: Build the Prompt

Take the user's request and use it as the copilot prompt. If the user provides /gco with arguments, use those as the prompt directly.

Step 2: Run Copilot

LOGDIR=$(node $HOME/.claude/scripts/get-logdir.js)
mkdir -p "$LOGDIR"
DATETIME=$(date +%Y%m%d_%H%M%S)
SLUG="<short-topic-slug>"

bash $HOME/.claude/skills/gco/scripts/gco-run.sh \
  "<prompt>" \
  "$LOGDIR/${DATETIME}-gco-${SLUG}.md" \
  "$LOGDIR/${DATETIME}-gco-${SLUG}-stderr.log"

Run as a background Bash task with 15-minute timeout.

Step 3: Collect and Present Results

Read the output file ($LOGDIR/${DATETIME}-gco-${SLUG}.md)
If empty or missing, check stderr log for errors — a no-quota (402) error means Copilot Premium is exhausted; report it and fall back to Claude Code tools
Synthesize and present findings to the user
Include the log file path for reference

Important Notes

Copilot cannot modify files — all writes are done by Claude Code
NEVER use ~ in paths — use $HOME
Output and stderr go to $LOGDIR/${DATETIME}-gco-* (timestamped)
If copilot is not installed, report "Copilot CLI not found. Install with: gh extension install github/gh-copilot" and fall back to Claude Code tools

このリポジトリの他の Skills

同じリポジトリ

issue-sweep

Takazudo/claude-resources

Sweep open GitHub issues — optionally narrowed by label — and drive each to completion via `/big-plan -m -a`. Collects candidates, triages out work that needs careful human judgment, confirms once, then handles the rest autonomously one issue at a time. Use when: (1) User says '/issue-sweep', 'sweep issues', 'sweep open issues', 'handle the open issues', 'clear the issue backlog', or 'do the issues', (2) The user wants to batch-process a label's worth of issues (e.g. `agent-found`, `mac`), (3) After a work round that left a pile of follow-up issues. Options: "`-f`/`--filter LABEL` keeps only issues carrying that label; `-ex`/`--exclude LABEL`" drops issues carrying it; with no options it sweeps ALL open issues. Locally-checkable "verify X" tasks are verified directly and closed (not run through `/big-plan`). Skips issues that need careful human judgment (huge multi-major version bumps, super-big epics, design calls); verification tasks that can't be auto-verified locally (auth/deploy/external/subjective) are

2026-06-2510

codex-imagegen

Takazudo/claude-resources

Generate or redesign raster images (PNG mockups, illustrations, photos, UI design polish) from inside Claude Code by driving Codex CLI's built-in $imagegen, billed to ChatGPT-included usage instead of per-image OpenAI API charges. Use whenever the user wants to create/generate an image, make a mockup or illustration, produce a photo, polish or redesign a UI from a screenshot, or get a PNG out of a session — even if they don't mention Codex or "imagegen". This is the preferred image-generation path because Anthropic models cannot generate raster images and this route avoids API billing.

2026-06-2210

design-polish-loop

Takazudo/claude-resources

Iterative visual design-polish loop for an existing or WIP web UI. Each round: capture the live page as screenshots, judge it from the rendered pixels, and apply CSS polish toward a better-looking target using /css-wisdom's tight-token strategy — then re-capture and compare. The target direction is set by codex-imagegen 'north-star' mockups generated from the current screenshot, so the loop pursues a genuinely better look instead of nudging the existing one in place. Use when: (1) user says 'design-polish-loop', 'polish loop', 'polish this page/design/UI', (2) user wants to level up / upgrade the look of a current design or WIP project, (3) user wants AI-proposed redesign directions applied to a real rendering page, (4) user calls a design plain, dated, flat, or unpolished and wants it improved. Main use case: improving the current design of a WIP project. It polishes what already renders — not brand-new-from-scratch pages.

2026-06-2210

dev-bump-zudo-deps

Takazudo/claude-resources

Bump every `@takazudo/*` registry dependency in the current project to its newest version, resolving each by the channel it currently tracks. Use when: (1) User says '/dev-bump-zudo-deps', 'bump zudo deps', 'bump the @takazudo packages', 'update zfb', 'update zudo-doc', or 'update the takazudo toolchain to latest', (2) A new `@takazudo/*` prerelease or release has shipped and this project should adopt it, (3) Routine first-party dependency-update rounds. Resolution rule: a dep currently on the `next` prerelease line (`0.1.0-next.N`) → newest `next` release; a dep on the literal `latest` tag → `dist-tags.latest`; a plain stable semver → newest stable. Skips `workspace:`/`file:`/`link:` specs and leaves operator style (exact / `^` / `~`) and prerelease channel intact. A bundled script does the discovery + semver resolution; this skill drives install + verify + report.

2026-06-2210

big-plan

Takazudo/claude-resources

Plan implementation by breaking work into one epic GitHub issue + child sub-issues. Use when: (1) User says '/big-plan', (2) User wants to plan an implementation before coding, (3) User wants to split a feature into small issues for parallel agent team work, (4) User references existing issues (e.g. 'implement issue #123', 'plan all open issues', 'plan recent 3 open issues'). Auto-reads project-scope l-lessons-* skills (from /retro-notes) before planning. Codex (-co) is the DEFAULT Step 5 plan reviewer — it runs even when no reviewer flag is passed; -op/-gco add more second opinions (runnable in parallel). Use -a/--auto to run the chain autonomously: skip the Step 6 confirmation wait (pausing only when something needs careful consideration), auto-create the issues, then auto-invoke the implementation skill in the same session — /x-wt-teams for a multi-sub-issue plan, /x-as-pr for a single-sub-issue plan — forwarding -a so multi-wave plans auto-chain wave after wave. Use -m/--merge to also merge the final PR i

2026-06-1810

dev-purge-gh-cache

Takazudo/claude-resources

Purge GitHub Actions caches across every non-archived repo for one or more GitHub owners (users or orgs). Use when (1) the user says "purge gh cache", "clear actions cache", "delete CI cache", or invokes /dev-purge-gh-cache, (2) the user wants to free up GitHub Actions cache storage for an account/org, (3) the user names one or more GitHub owners (e.g. "Takazudo", "zudolab") and asks to wipe their Actions caches. Handles fan-out across all repos, parallel survey, bulk delete, and real-time verification.

2026-06-1810

name	gco
description	Run GitHub Copilot CLI as a read-only sub-agent from Claude Code. Use when: (1) User says 'gco', 'copilot', or 'ask copilot', (2) Delegating code review or research to Copilot, (3) Getting a second opinion on code or architecture. Read-only mode (no file writes), gpt-5.4 model.
user-invocable	true
argument-hint	<prompt>
allowed-tools	["Bash(bash )","Bash(timeout )","Bash(gtimeout )","Bash(node )"]

GitHub Copilot Read-Only Sub-Agent

Run GitHub Copilot CLI in read-only mode for code review, research, and investigation tasks.

How It Works

Copilot runs non-interactively with -p (prompt) and -s (silent output)
Read-only enforced via --deny-tool='write' (hard tool-level block) and read-only preamble in prompt
Uses --no-ask-user and --allow-all-tools for fully autonomous execution
Model: gpt-5.4
Timeout: 15 minutes

Process

Step 1: Build the Prompt

Take the user's request and use it as the copilot prompt. If the user provides /gco with arguments, use those as the prompt directly.

Step 2: Run Copilot

LOGDIR=$(node $HOME/.claude/scripts/get-logdir.js)
mkdir -p "$LOGDIR"
DATETIME=$(date +%Y%m%d_%H%M%S)
SLUG="<short-topic-slug>"

bash $HOME/.claude/skills/gco/scripts/gco-run.sh \
  "<prompt>" \
  "$LOGDIR/${DATETIME}-gco-${SLUG}.md" \
  "$LOGDIR/${DATETIME}-gco-${SLUG}-stderr.log"

Run as a background Bash task with 15-minute timeout.

Step 3: Collect and Present Results

Read the output file ($LOGDIR/${DATETIME}-gco-${SLUG}.md)
If empty or missing, check stderr log for errors — a no-quota (402) error means Copilot Premium is exhausted; report it and fall back to Claude Code tools
Synthesize and present findings to the user
Include the log file path for reference

Important Notes

Copilot cannot modify files — all writes are done by Claude Code
NEVER use ~ in paths — use $HOME
Output and stderr go to $LOGDIR/${DATETIME}-gco-* (timestamped)
If copilot is not installed, report "Copilot CLI not found. Install with: gh extension install github/gh-copilot" and fall back to Claude Code tools