Dead code removal via parallel scanning, reference verification, batch execution, and atomic commits. You are the ORCHESTRATOR — you scan, verify, batch, then delegate ALL removals.
日本語の概要は準備中です。原文の説明を表示しています。
2,494 件 ・ 関連度順
概要と使いどころ
Dead code removal via parallel scanning, reference verification, batch execution, and atomic commits. You are the ORCHESTRATOR — you scan, verify, batch, then delegate ALL removals.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically infer loop invariants for code verification and correctness proofs. Use when analyzing loops to identify properties that hold throughout execution, generating assertions for verification, proving loop correctness, or documenting loop behavior. Supports Python, Java, C/C++, and language-agnostic analysis. Generates invariants as code assertions (assert statements). Triggers when users ask to infer invariants, find loop properties, generate loop assertions, prove loop correctness, or verify loop behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Performs abstract interpretation over source code to infer possible program states, variable ranges, and data properties without executing the program. Reports potential runtime errors including out-of-bounds accesses, null dereferences, type inconsistencies, division by zero, and integer overflows. Use when analyzing code for potential runtime errors, performing static analysis, checking safety properties, or verifying program behavior without execution.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes code to identify security-critical time intervals and timing vulnerabilities in authentication, authorization, and time-sensitive security operations. Use this skill when reviewing code for proper timeout enforcement, token expiration, session management, rate limiting, password reset validity, or any time-sensitive security mechanism. Detects missing expiration checks, excessive timeout values, lack of rate limiting, client-side only validation, hardcoded timeouts, and timing attack vulnerabilities. Triggers when users ask to check security timeouts, verify token expiration handling, audit session timeout implementation, review rate limiting, or analyze time-based security controls.
日本語の概要は準備中です。原文の説明を表示しています。
Translate C/C++ programs to equivalent Dafny code while preserving semantics and ensuring verification. Use when users ask to convert, translate, or port C/C++ code to Dafny, or when they need to formally verify C/C++ algorithms using Dafny's verification capabilities. Handles functions, structs, pointers, arrays, memory management, and ensures the generated Dafny code is well-typed, executable, verifiable, and can successfully run.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically repair buggy code and generate comprehensive tests for Python, Java, and C++ programs. Use when users need to fix logic errors or runtime errors in functions, modules, or repositories. Accepts specifications via natural language descriptions, existing test cases, or input/output examples. Generates corrected code, creates or updates tests to verify correctness and prevent regressions, and produces a detailed report explaining the bug, fix, and testing strategy. Triggers on requests like "fix this bug", "repair this code", "debug this function", or "this code is broken".
日本語の概要は準備中です。原文の説明を表示しています。
Verify GDD, UX, Architecture, and Epics alignment before production. Use when the user says "check readiness" or "implementation readiness"
日本語の概要は準備中です。原文の説明を表示しています。
Create, inspect, convert, apply, replace, verify, troubleshoot, update, publish, or restore reversible CodeDrobe themes for supported Chromium/Electron AI desktop apps, including OpenAI Codex, Tencent WorkBuddy, QoderWork (CN/global), and TRAE SOLO (global/CN). Use when a user asks to turn an attached or local reference image into a Codex, WorkBuddy, QoderWork, or TRAE SOLO skin, reproduce a visual style with native UI, build a multi-app theme, work with .codedrobe-theme packages or theme images, analyze a live CDP DOM snapshot, repair DOM compatibility failures, use a custom port or installation path, capture verification screenshots, search the CodeDrobe store or install a store theme by name, publish or submit a theme to the CodeDrobe store, or migrate a legacy .codex-theme file.
日本語の概要は準備中です。原文の説明を表示しています。
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Verify all outputs exist after creating a new component and fix any issues
日本語の概要は準備中です。原文の説明を表示しています。
Verify application state with AI-powered assertions
日本語の概要は準備中です。原文の説明を表示しています。
Locate elements and verify app state with AI-powered assertions
日本語の概要は準備中です。原文の説明を表示しています。
Iteratively study and apply elegant coding patterns. Each iteration - understand the code, research what simple and elegant code looks like, apply learnings, verify with CI. Use as a standalone refactoring pass or when the user asks to make code more elegant, simple, or idiomatic.
日本語の概要は準備中です。原文の説明を表示しています。
Verify app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.
日本語の概要は準備中です。原文の説明を表示しています。
Find scientific papers, follow citations, and verify claims against paper passages. Use for literature questions, related work, citing papers, references, or a question about a particular scientific paper.
日本語の概要は準備中です。原文の説明を表示しています。
Semi-automated fact-checking, source credibility evaluation, misinformation detection, prebunking, and evidence-ledger based claim verification. Use when a user asks to verify a claim, article, social post, screenshot, URL, quote, data point, compare sources, detect manipulation, evaluate source reliability, or generate an HTML fact-check card/share-safe correction. Supports text, URLs, screenshots/images, two-source comparison, and topic-level prebunking in Bulgarian, English, Russian, EU policy, health, science, and geopolitical contexts. Trigger phrases: "is this true?", "is this fake?", "fact check this", "compare these sources", "проверка на факти", "истина ли е", "дезинформация ли е", "сравни тези източници".
日本語の概要は準備中です。原文の説明を表示しています。
Create QA checklists for verifying design implementation accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Verify fix commits address audit findings without new bugs
日本語の概要は準備中です。原文の説明を表示しています。
Repo-local workflow skill for large coding tasks. Initializes .agent/tasks/TASK_ID artifacts, installs project-scoped Codex and Claude subagents, updates AGENTS.md plus the repo's Claude guide file with the workflow, and runs a spec-freeze → build → evidence → verify → fix loop with fresh-session verification.
日本語の概要は準備中です。原文の説明を表示しています。
Use whenever you need to understand how this theme works — adding pages, managing content, configuring the site, using partials/components/modules, project architecture, scripts, or styling/theming (Tailwind v4, Bootstrap 5, or a hybrid — verify which). Use for ANY question about the structure, usage, or customization of the template or theme.
日本語の概要は準備中です。原文の説明を表示しています。
Use when testing a bundle-plugin locally before release — generating dev-marketplace environments, verifying component discovery, running hook smoke tests, and validating cross-platform readiness
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user wants a TikZ figure for a paper — an icon, an editable architecture/pipeline/flow template, or an example — and wants you to find, edit, and verify it. The single repo-wide skill for working with the OpenTikZ library.
日本語の概要は準備中です。原文の説明を表示しています。
Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and type-checker clean, keep the build and tests green, make interface changes additive, protect security invariants).
日本語の概要は準備中です。原文の説明を表示しています。