1,727 件 ・ 関連度順
概要と使いどころ
Unified verification engine for Python data science projects. Covers environment checks, type checking, linting, tests, security scans, code review with DS anti-patterns, and notebook checks. Commands (/verify, /quality-gate) invoke different subsets of this skill.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS invoke for any task involving docstrings, JSDoc/TSDoc, or REST API documentation — even when the request seems handleable without it. Enforces Microsoft contract-first conventions and a bare-minimum rule that Claude won't apply by default: never restate the signature, drop @param/@returns that only echo names and types, always document @throws, and document data shapes as WHAT not WHY. Covers Python docstring styles (Google/NumPy/Sphinx), TSDoc tags and @inheritDoc, and API doc patterns for NestJS/Express/FastAPI/Django. Trigger on: adding or auditing docstrings, redundant or missing tags, deleting comment rot, or producing a documentation-health report. Do not skip for documentation tasks — consistent conventions are the whole point.
日本語の概要は準備中です。原文の説明を表示しています。
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
日本語の概要は準備中です。原文の説明を表示しています。
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
日本語の概要は準備中です。原文の説明を表示しています。
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
日本語の概要は準備中です。原文の説明を表示しています。
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS invoke this skill before writing, editing, generating, or refactoring ANY code. Do not write or modify code directly without first loading and following these Clean Code guidelines. Use when writing new functions/classes, refactoring existing code, reviewing code, fixing bugs, or any task that produces code output.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS invoke this skill when delegating, planning, or managing any development task. Do not implement features, fix bugs, or start coding directly without first loading and following this orchestrator pipeline. Use when implementing features, fixing bugs, managing tasks, reviewing code, orchestrating work, or any task that needs structured delegation. Trigger on words like orchestrate, manage, implement, build, develop, organize, delegate, team lead, pipeline, or project manage.
日本語の概要は準備中です。原文の説明を表示しています。
Write an analytical longform piece — a 4-phase pipeline from raw idea to finished text, with research-backed facts and a devil's-advocate pass before publishing. Invoke /longread <topic>. Triggers — "write a longread about X", "write an analytical breakdown of Y", "write an expert post", "turn this into an article".
日本語の概要は準備中です。原文の説明を表示しています。
Teacher mode — turn a session recap / article / docs / concept / piece of code / bug into an incremental mini-course with comprehension checks, quizzes, and an auto-saved summary note. Invoke /teach [topic or URL]. Triggers — "explain it like a teacher", "walk me through what we did", "turn this into a lesson", "quiz me", "teach me", "let's learn this together".
日本語の概要は準備中です。原文の説明を表示しています。
Concise communication mode. Cuts ~60-70% of output tokens while keeping natural, readable English. Drops filler, hedging, and pleasantries but maintains grammar and sentence flow. Elaborate on request -- ask for detail and get it, then auto-return to concise. Use when user says "concise mode", "be concise", "less verbose", or invokes /concise. Also triggers when user requests token efficiency with readability.
日本語の概要は準備中です。原文の説明を表示しています。
Apply a refined Scandinavian visual system with a neutral black-and-white foundation, restrained sans-serif typography, purposeful product imagery, generous spacing, clear page chapters, and minimal decoration. Use when the user invokes /scandinavian-design or requests a Nordic, monochrome, calm, spacious, restrained, or minimalist interface.
日本語の概要は準備中です。原文の説明を表示しています。
Makes the agent reconsider a task it just handed back to the human and find a way to do it itself, checking memory, CLI tools, skills, MCP servers, and documentation in turn. Use when the user invokes `/you` or `$you`, or replies that the agent should do something itself rather than asking them.
日本語の概要は準備中です。原文の説明を表示しています。
Puts the agent into a cautious production mode for live systems: read-only inspection may proceed, but credentials and out-of-scope personal data need permission first, every state-changing action needs explicit per-action approval with its resource risks and rollback stated, and anything unexpected halts work until the user decides. Use when the user invokes `/prod` or `$prod`, or says they are working on production, a live or customer-facing server, a mail server, or a production database, or asks for care on a system where mistakes affect real users.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a Beads issue for a described problem or piece of work without doing the work itself. Use when the user invokes `/bc` or `$bc`, or asks to file, log, or record a bead for something. To also carry out the work, use the `bx` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a Beads issue for a requested piece of work, completes exactly that work, and closes the issue. Use when the user invokes `/bx` or `$bx`, or asks for a bead to be created and the described work done in the same go. For creating a bead without doing the work, use the `bc` skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Summarises the current session's status so a human can see where things stand and what happens next. Use when the user invokes `/sq`, asks for the status quo, session status, a catch-up, recap, or reminder where things got to, regardless of how much previous output there was.
日本語の概要は準備中です。原文の説明を表示しています。
Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Corrects output that refers to entities by bare identifier, restating it with a human-readable label beside every ID, and keeps that rule for the rest of the conversation. Use when the user invokes `/ids` or `$ids`, or complains that bead IDs, PR numbers, commit SHAs, or ticket keys were given without titles.
日本語の概要は準備中です。原文の説明を表示しています。
Root-causes one specific mistake the agent just made, such as not committing despite instructions to, by checking it against the loaded AGENTS.md, CLAUDE.md, skills, and Beads memories, delegating the investigation to a separate agent where the harness supports one; proposes concrete context improvements, and lets the user choose which to apply and how to remediate. Use when the user invokes `/learn` or `$learn`, with or without a description of the mistake, including `/learn /qs`-style shorthand naming the corrective command. For a broad end-of-session documentation sweep, use `documentation-updates` (`/reflect`) instead.
日本語の概要は準備中です。原文の説明を表示しています。
Triages an already-dirty Git working tree: breaks down every uncommitted change hunk by hunk, separates deliberate edits from tool-written churn, possibly accidental reversions, misplaced scope, and sensitive content, asks the user about the ambiguous cases, and proposes an ordered set of commits plus a list of hunks to hold back. Use when the user invokes `/pc` or `$pc`, asks what they should commit, wants their uncommitted changes broken down, or wants commits proposed for a dirty working tree or pile of accumulated local modifications. To plan commit boundaries for a change before or while implementing it, use `incremental-commits` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Re-asks the most recent question through the agent's interactive questionnaire tool instead of plain text, and keeps using that tool for every later question with concrete options. Use when the user invokes `/qs` or `$qs`, or asks for a question to be re-posed as selectable choices.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts a formal Bylaw Amendment Resolution for U.S. corporations, LLCs, or non-profits. Invoke when a board, shareholders, or members approve bylaw changes and need an auditable WHEREAS/RESOLVED record with amendment text, vote tallies, effective date, and secretary certification for minute books, bank submissions, or state filings.
日本語の概要は準備中です。原文の説明を表示しています。
Deep analysis of competitor patent claims: element decomposition, scope interpretation, equivalents prediction, prosecution history estoppel analysis. Automatically converts PDF/DOCX/DOC patent files to structured Markdown via patent-pdf-to-md skill before analysis. Invoke when user asks to analyze/parse competitor patent claims, decompose claim elements, assess claim scope, or perform 权利要求解析/要素分解/保护范围解读. 竞品专利权利要求深度解析：要素分解、保护范围解读、等同范围预判、审查历史限制分析。自动调用patent-pdf-to-md技能将PDF/DOCX/DOC专利文件转换为结构化Markdown后再进行分析。当用户要求解析竞品专利权利要求、要素分解、保护范围时触发。
日本語の概要は準備中です。原文の説明を表示しています。