1.4万 件 ・ 人気順
概要と使いどころ
Use when pinning or unpinning the CLI version the Kilo JetBrains plugin uses, or fresh-regenerating the local repo CLI. Cleans all leftover CLI binaries and build artifacts in the current worktree so every operation starts from a fresh, artifact-free state.
日本語の概要は準備中です。原文の説明を表示しています。
Review code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
日本語の概要は準備中です。原文の説明を表示しています。
Formats plain text or markdown files with frontmatter, titles, summaries, headings, bold, lists, and code blocks. Use when user asks to "format markdown", "beautify article", "add formatting", or improve article layout. Outputs to {filename}-formatted.md.
日本語の概要は準備中です。原文の説明を表示しています。
Extracts resources and JavaScript from any installed Electron app (`.asar` bundle), restoring original sources from `.js.map` files when available or formatting minified code with Prettier otherwise. Use when user wants to "extract Electron app", "decompile Electron", "get the source code of <app>", "inspect app.asar", "看 Electron 应用源码", "提取 .asar", or asks how a desktop Electron app is built. Skips `node_modules` and supports both macOS and Windows.
日本語の概要は準備中です。原文の説明を表示しています。
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
日本語の概要は準備中です。原文の説明を表示しています。
Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.
日本語の概要は準備中です。原文の説明を表示しています。
Localization pipeline — find hardcoded strings, extract string tables, cultural review, VO, RTL, enforce string freeze.
日本語の概要は準備中です。原文の説明を表示しています。
Author the architecture blueprint before code is written. Validates decisions against the pinned engine, flags knowledge gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural code review — coding standards, SOLID, testability, performance concerns.
日本語の概要は準備中です。原文の説明を表示しています。
Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch, PR, or commit. Use when starting isolated work or isolating an existing ref.
日本語の概要は準備中です。原文の説明を表示しています。
Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.
日本語の概要は準備中です。原文の説明を表示しています。
Take a request all the way to done, hands-off, through the right Compound Engineering skills. A code change ends as an open pull request, pushed without stopping. Use only when the user explicitly asks for autonomous end-to-end work or invokes lfg directly. Use ce-plan, ce-work, ce-debug, or ce-commit-push-pr for work the user reviews step by step.
日本語の概要は準備中です。原文の説明を表示しています。
Explain the last message, or a supplied file, link, or passage, in plain language a person follows on the first read. Use when the user invokes wtf because they did not follow something. Use ce-explain to investigate how or why code works, and ce-noslop to rewrite prose.
日本語の概要は準備中です。原文の説明を表示しています。
Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified. Use when addressing feedback already left on a PR, preparing local fixes for a caller to publish, or completing a saved feedback batch. Use ce-code-review for reviewing code before feedback exists.
日本語の概要は準備中です。原文の説明を表示しています。
Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.
日本語の概要は準備中です。原文の説明を表示しています。
Babysits an open GitHub PR until merge-ready. Use when asked to watch a PR over time — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.
日本語の概要は準備中です。原文の説明を表示しています。
Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Connect to Pascal and use its MCP tools to create, inspect, edit, validate, save, or hand off editable 3D building scenes. Use this skill whenever a user asks an agent to work in Pascal, make a room or building model, inspect a Pascal project, perform spatial edits, connect Pascal MCP, or return a verified Pascal editor link. It also governs safe local, existing-account, and explicitly authorized autonomous setup.
日本語の概要は準備中です。原文の説明を表示しています。
Screen a pull request from an outside contributor for hidden, obfuscated, or supply-chain-risky changes before any of its code runs.
日本語の概要は準備中です。原文の説明を表示しています。
Create an OpenCode plugin for OpenWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
日本語の概要は準備中です。原文の説明を表示しています。
Cut an OpenWork release, release the app, publish a new version, rerun or recover a release tag, verify release assets. Tag-driven GitHub Actions release that makes zero commits to the repo.
日本語の概要は準備中です。原文の説明を表示しています。
Connect the OpenWork MCP Gateway (https://api.openworklabs.com/mcp/agent) to Claude Code, Codex, Gemini CLI, Cursor, VS Code, Claude Desktop, or ChatGPT so the agent can use the user's OpenWork organization skills, plugins, and connections.
日本語の概要は準備中です。原文の説明を表示しています。