2,073 件 ・ 関連度順
概要と使いどころ
Migrate Java EE javax.* imports to Jakarta EE jakarta.* namespace. Use when upgrading to Spring Boot 3.x, migrating javax.persistence, javax.validation, javax.servlet imports, or fixing compilation errors after Jakarta EE transition. Covers package mappings, batch sed commands, and verification steps.
日本語の概要は準備中です。原文の説明を表示しています。
Automated Planning utilities for loading PDDL domains and problems, generating plans using classical planners, validating plans, and saving plan outputs. Supports standard PDDL parsing, plan synthesis, and correctness verification.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive test cases including edge cases, stress tests, and counter-examples for algorithm correctness verification. Supports random generation, constraint-based generation, and brute force oracle comparison.
日本語の概要は準備中です。原文の説明を表示しています。
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs. Evidence before assertions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when receiving code review feedback, before implementing suggestions. Requires technical rigor and verification, not blind implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomously engage with complex coding tasks — multi-step planning, tool use, self-correction, and solution verification without human intervention.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor PR lifecycle from creation through merge including CI monitoring, review comment handling, thread resolution, and merge readiness verification.
日本語の概要は準備中です。原文の説明を表示しています。
Technical debt management including branch cleanup, doc verification, TODO scanning, and dependency auditing
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence requirement enforcement ensuring all claims are backed by logs, test results, or exit codes. Zero = success, non-zero = failure. No guessing allowed.
日本語の概要は準備中です。原文の説明を表示しています。
Execute one complex task as ordered, dependent steps run sequentially, passing context from each step to the next, with per-step LLM-as-a-judge verification. Use when later steps depend on the results of earlier ones.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a task step by step with automated LLM-as-Judge verification at the end of each phase
日本語の概要は準備中です。原文の説明を表示しています。
Reflect on previus response and output, based on Self-refinement framework for iterative improvement with complexity triage and verification
日本語の概要は準備中です。原文の説明を表示しています。
Launch an intelligent sub-agent with automatic model selection based on task complexity, specialized agent matching, Zero-shot CoT reasoning, and mandatory self-critique verification
日本語の概要は準備中です。原文の説明を表示しています。
Execute a task with sub-agent implementation and LLM-as-a-judge verification with automatic retry loop
日本語の概要は準備中です。原文の説明を表示しています。
Run independent tasks concurrently across multiple files or targets using parallel sub-agents, with per-task model selection and LLM-as-a-judge verification. Use when tasks do not depend on each other and can run side by side.
日本語の概要は準備中です。原文の説明を表示しています。
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Expert web researcher using advanced search techniques and synthesis. Masters search operators, result filtering, and multi-source verification. Handles competitive analysis and fact-checking. Use PROACTIVELY for deep research, information gathering, or trend analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Audit a UI or design against WCAG 2.2 AA/AAA and ARIA patterns, returning criterion-referenced findings with severity and specific fixes. Use when the user wants an accessibility check, contrast verification, keyboard/screen-reader review, or wants to confirm a component meets POUR.
日本語の概要は準備中です。原文の説明を表示しています。
The house rules for ANY design or UI work - the verification protocol (run the gate, never claim a number), the absolute no-emoji rule, token by intent, one shared theme, the eight states, one thing leads, and output completeness. Load this FIRST whenever building, reviewing, or theming a screen, component, or token set. Installed as a plugin, this skill carries what CLAUDE.md carries in the repo.
日本語の概要は準備中です。原文の説明を表示しています。
Validate bibliography entries against citations in all lecture files. Structural checks (missing/unused entries, malformed fields) by default; `--semantic` adds citation-drift detection, DOI verification, and style-consistency checks.
日本語の概要は準備中です。原文の説明を表示しています。
Run Chain-of-Verification (CoVe) on a draft or a block of text with factual claims. Spawns the `claim-verifier` agent in a fresh context (never a conversation fork) so it never sees the draft — then reports which claims are supported, contradicted, or unverifiable. Use when user says "verify these citations", "check the claims in X", "did I hallucinate anything", "fact-check this draft", "run CoVe on this", or after any text generation that asserts facts about papers, datasets, or numerical results. NOT for style/grammar review (use `/proofread`) or substance review (use `/review-paper`).
日本語の概要は準備中です。原文の説明を表示しています。
Read-only R code review protocol for `.R` scripts. Checks code quality, reproducibility, domain correctness, tidyverse idioms, and professional standards; produces a report without editing. Use when user says "review this R script", "check the R code", "audit the analysis code", "code review on the R", or when an R file is touched as part of a paper submission. NOT for running the code — pair with `/audit-reproducibility` for numeric verification.
日本語の概要は準備中です。原文の説明を表示しています。
Use when verifying that a generated agent package can be installed, discovered by runtimes, and checked without private dependencies.
日本語の概要は準備中です。原文の説明を表示しています。