「files」の検索結果

Improve agent harness configuration based on recent friction points. Use when invoked as `$retro` or when the user asks for autonomous cleanup of Codex, agent harness, or migrated Claude configuration.

日本語の概要は準備中です。原文の説明を表示しています。

Run an infrastructure-first security audit of a repository - secrets archaeology, dependency supply chain, CI/CD pipeline, LLM/AI attack surface, agent skill supply chain, OWASP Top 10, STRIDE threat model, and data classification - with a confidence gate and a pre-emit verification gate that suppress speculative findings. Use when asked for a security audit, threat model, pentest-style review, OWASP pass, or a pre-release security check. Not for reviewing a single diff - use requesting-code-review for that.

日本語の概要は準備中です。原文の説明を表示しています。

Pin the current cmux workspace to the done lane with `cmux workspace status set done` once a session goal is reached and verified. Use at the end of a work session running inside a cmux terminal, right before the final response; skip when work is blocked, handed off, awaiting user input, or when nothing was changed.

日本語の概要は準備中です。原文の説明を表示しています。

Use when executing implementation plans with independent tasks in the current session

日本語の概要は準備中です。原文の説明を表示しています。

Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.

日本語の概要は準備中です。原文の説明を表示しています。

Codex workflow tips from Boris Cherny (creator of Codex) and the Codex team. Use when: setting up Codex, optimizing workflows, running parallel sessions, configuring AGENTS.md, using skills/commands, subagents, hooks, MCP integrations, or learning best practices. Covers: git worktrees, plan mode, verification, permissions, Slack MCP, BigQuery, prompting tips, plugins, custom agents, sandboxing, keybindings, status lines, output styles, customization, /simplify for code quality, /batch for parallel code migrations, /loop for scheduled tasks, code review agents, /btw for mid-task questions, /effort max reasoning, remote control sessions, voice mode, setup scripts, session naming, /color, PostCompact hook, auto mode, /schedule cloud jobs, iMessage plugin, auto-memory, and auto-dream, mobile app, session teleporting, Cowork Dispatch, Chrome extension, Desktop app, /branch forking, --bare SDK startup, --add-dir multi-repo, --agent custom agents, /voice input.

日本語の概要は準備中です。原文の説明を表示しています。

Investigate and fix failing CI. Takes a PR reference, one or more CI run/job URLs, or freeform text describing where the failures are, then enumerates failing workflows/jobs/steps, determines the root cause (often one shared cause behind several red checks), proposes a fix plan, applies code changes, commits, pushes, watches the new runs, and repeats until checks pass. Use when the user says "fix CI", "CI is red", "checks are failing", "the build is broken on my PR", "fix the failing jobs", or pastes a failing CI run URL. Do NOT use for authoring new workflows, or for read-only diagnosis with no fix intent — use gha-log-reader for that.

日本語の概要は準備中です。原文の説明を表示しています。

Audit one or all supported agent harnesses (claude, codex, opencode, pi, omp, antigravity, cursor, grok) for config efficiency, hook overhead, permission friction, plugin and MCP cost, skill metadata portability, dead config, and measured session friction. Use when invoked as `$optimize-harness [harness ...] [focus]`, or when the user asks to optimize or compare agent harness configuration.

日本語の概要は準備中です。原文の説明を表示しています。

PR formatting reference — title, body template, label mapping, assignment, and draft policy. Invoked by pr/create and pr/update-desc commands to ensure consistent PR formatting.

日本語の概要は準備中です。原文の説明を表示しています。

No-op workflow for when the user says they duplicated the chat/session into another tab. Use when invoked as `$dupe` or when the user says this tab was duplicated and no action is needed.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you have a written implementation plan to execute in a separate session with review checkpoints

日本語の概要は準備中です。原文の説明を表示しています。

Coordinate multi-agent work through durable artifacts in git instead of chat. Use this whenever a task involves sending a message to another agent, agent mailboxes or handoffs, claiming work from a shared queue, notifying another agent or crew (OpenClaw, Grok Bot, Claude Code, Codex, Gas Town/Gas City workers) that work is ready, or whenever the user mentions the artifact bus, message bus, agent mail, beads mail, doorbells, or pings between agents — even if they don't say "bus" explicitly.

日本語の概要は準備中です。原文の説明を表示しています。

Drive QA of a SwiftUI app on a real iPhone over USB - screenshot, read the accessibility tree, inspect @Observable state, tap, swipe, and type through an HTTP bridge embedded in the app under test. Use when asked to test an iOS app on a physical device, find bugs on the device, or expose a connected iPhone to a remote agent over Tailscale. Requires the ios-agent-qa runtime; not for simulator or XCTest work.

日本語の概要は準備中です。原文の説明を表示しています。

Research one agent harness's release (docs, source, runtime) and fill its capability cells in scripts/harness_capabilities.py with cited evidence. Use after a harness version bump, when just harness-probe reports re-research, or when capability cells read unknown.

日本語の概要は準備中です。原文の説明を表示しています。

Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Quick-save the last assistant response as a verbatim note in the 2ndBrain Obsidian vault (~/2ndBrain/quick-notes/<year>/). Use when the user asks to quick-save/save the last response to 2ndBrain, or invokes $2ndbrain or /skill:2ndbrain.

日本語の概要は準備中です。原文の説明を表示しています。

Create and commit a durable handoff document that gives a fresh agent the context and prompt to continue the current planning or implementation work. Use only when explicitly invoked as `$handoff` or when the user explicitly requests a handoff.

日本語の概要は準備中です。原文の説明を表示しています。

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

日本語の概要は準備中です。原文の説明を表示しています。

Retrieve current documentation, API references, and code examples for any library, framework, SDK, CLI tool, or cloud service — including well-known ones like React, Next.js, Prisma, Django, or Spring Boot. Use for API syntax, configuration options, version migrations, setup instructions, and library-specific debugging, even when you already think you know the answer: training data on API details and signatures is frequently outdated. Prefer this over web search for library documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Paseo reference for managing projects, workspaces, workspace scripts, agents, schedules, and heartbeats.

日本語の概要は準備中です。原文の説明を表示しています。

Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.

日本語の概要は準備中です。原文の説明を表示しています。

A relentless interview to sharpen a plan or design.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnoses failing GitHub Actions runs by reading logs, identifying the root cause, and suggesting fixes. Use this skill whenever a user shares a GHA run URL, pastes runner log output, mentions a failing workflow, asks why a CI job is broken, or says anything like "my GHA is failing", "workflow failed", "can you check my run", or "CI is broken". Also trigger when raw log text is detected in the conversation that appears to come from a GitHub Actions runner. Do NOT use for general GHA workflow authoring questions, YAML formatting help, or passing runs with no failure context.

日本語の概要は準備中です。原文の説明を表示しています。

Check GitHub Actions CI status for PRs and branches. Use when the user asks "did CI pass", "check status", "what failed", "are checks green", "PR checks", "CI status", "workflow status", "re-run jobs", or wants a quick summary of GitHub Actions runs for a PR or the current branch.

日本語の概要は準備中です。原文の説明を表示しています。