1,319 件 ・ 関連度順
概要と使いどころ
Audit the repository or a broad subsystem for security, correctness, and maintainability risks. Use for audit requests or /audit; use review for a specific change and vuln-check for a security-only assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to open or preview a single markdown file that is not part of an OpenKnowledge project, wants to share an OpenKnowledge project with collaborators, asks whether OpenKnowledge supports a particular capability, or asks how `ok init` / `ok cowork` / OK Desktop set up a project. Do NOT load to perform OpenKnowledge reads/writes — the runtime guidance for editing markdown inside an initialized OK project ships as a separate project-local skill installed into each detected agent's skills dir (for example `.claude/skills/open-knowledge/`) whenever `ok init` runs.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-repository coordination, synchronization, and architecture management with AI swarm orchestration
日本語の概要は準備中です。原文の説明を表示しています。
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
日本語の概要は準備中です。原文の説明を表示しています。
Repository conventions for commits, pull requests, and tests in this example project.
日本語の概要は準備中です。原文の説明を表示しています。
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI. Use after BB feature changes or when asked to verify or smoke-test BB. The feature map covers core UI and agent interfaces, every repository plugin, desktop, mobile, and hosted services; select the affected recipes and platform prerequisites.
日本語の概要は準備中です。原文の説明を表示しています。
Review system architecture, simplify boundaries, or compare interface designs from repository evidence
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate project or repository renames and moves involving Git, BB, services, or multiple machines. Preserve work and history while updating operational paths. Excludes ordinary file, code-symbol, and thread-title renames.
日本語の概要は準備中です。原文の説明を表示しています。
Qualify the exact final diff for a LoopX-managed goal. Use when goal policy enables change_quality_qualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt. The workflow is language-neutral, permits at most one policy-authorized safe-fix pass, and never grants merge or repository authority.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect GitHub pull requests, issues, workflow runs, and API data with the gh CLI. Use when the user wants repository facts from GitHub without opening the browser, especially for PR status, CI failures, issue lists, or structured JSON output.
日本語の概要は準備中です。原文の説明を表示しています。
Review an explicitly identified Marin pull request against the repository's correctness and maintainability expectations.
日本語の概要は準備中です。原文の説明を表示しています。
Run the repository self-improvement scrub only from its scheduler or an explicit request for that scrub.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze repository structure, patterns, conventions, and documentation for understanding a new codebase
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive PR descriptions following repository templates
日本語の概要は準備中です。原文の説明を表示しています。
Analyze logs and source from a completed repository example run. Never execute or control examples.
日本語の概要は準備中です。原文の説明を表示しています。
Review completed implementation changes before final verification. Use when repository policy requires independent review or the user explicitly requests it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when fixing invoice total calculations in the sandbox quickstart repository.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate GitHub security incidents using tamper-proof GitHub Archive data via BigQuery. Use when verifying repository activity claims, recovering deleted PRs/branches/tags/repos, attributing actions to actors, or reconstructing attack timelines. Provides immutable forensic evidence of all public GitHub events since 2011.
日本語の概要は準備中です。原文の説明を表示しています。
Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTI_CLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging, i18n harnesses, and production package validation. For simple package creation or repair, use tutti-workspace-app-factory instead.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and render fanout, implement semantically safe fixes, and verify behavior plus repository budgets. Use for trace files, reported profiling durations or call chains, dropped frames, long tasks, resize or scroll jank, render storms, layout thrashing, selector hot paths, interaction latency, or requests to locate exact source-level bottlenecks.
日本語の概要は準備中です。原文の説明を表示しています。
Audit, design, write, materially revise, or remove Tutti tests. Use whenever Codex changes or reviews unit, component, conformance, integration, regression, platform, or repository tests; enforce a protected product contract, credible failure, correct owning boundary, negative-control evidence, overlap review, deterministic setup, and an executing CI lane.
日本語の概要は準備中です。原文の説明を表示しています。
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when migrating applications, examples, integrations, documentation, manifests, or repository code from NeMo Flow to NeMo Relay across Python, Rust, Node.js, Go, C FFI, CLI, configuration, and observability surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.
日本語の概要は準備中です。原文の説明を表示しています。