1.9万 件 ・ 関連度順
概要と使いどころ
Review gate for correctness, reuse, and simplification. Produces a structured verdict with actionable findings. Trigger on any PR before merge, or on any agent-generated code before it is committed.
日本語の概要は準備中です。原文の説明を表示しています。
Measure real frontend performance — Core Web Vitals (LCP, CLS, INP), page-load traces, CPU and network throttling, Lighthouse accessibility/SEO scores, and heap growth — using chrome-devtools-mcp against a live browser. Trigger when asked "is the page fast enough", "measure Core Web Vitals", "why is this route slow", "run Lighthouse", "check for a memory leak", before any performance-gated certification (Built for Shopify, Core Web Vitals thresholds, store listing review), and before any launch or traffic-multiplier event. Measurement only — this skill never drives functional journeys.
日本語の概要は準備中です。原文の説明を表示しています。
Bilingual JD/CV/Resume tailoring and resume polish skill for job applications. Use when the user provides a job description, JD, role posting, existing CV/resume, LinkedIn profile, portfolio, or career notes and wants to optimize, rewrite, polish, or customize a resume/CV for ATS keywords, recruiter screening, interview-ready evidence, and role fit. 适用于根据招聘 JD、岗位描述、目标公司、现有简历/CV/LinkedIn/profile 进行简历优化、简历润色、岗位匹配、ATS 关键词映射、经历深挖、项目证据提炼和中英文求职简历定制。
日本語の概要は準備中です。原文の説明を表示しています。
Learns a user's personal writing and speaking style through interactive writing prompts, then generates a reusable voice profile. Use when the user says "learn my writing style," "write like me," "capture my voice," "voice calibration," "mimic my tone," "my writing style," or wants AI to match their personal communication style. Also activates when a .voice-profile.md file exists and the user asks you to write something in their voice.
日本語の概要は準備中です。原文の説明を表示しています。
Splits scarce time, budget or traffic across competing products, channels, campaigns or variants by treating them as a multi-armed bandit - Thompson sampling over beta posteriors, with optimism for anything not yet tried enough to judge. Use when deciding what to work on next, how to divide a marketing budget, which product to prioritise, whether to kill something that is underperforming, or when picking a winner among test variants.
日本語の概要は準備中です。原文の説明を表示しています。
Implement and finalize one ready rolling-wave slice in one invocation while preserving the lifecycle boundary between implementation and independent review. Use when the user wants a slice delivered end to end without manually invoking implement-slice and finalize-slice, wants main-local implementation by default with workers only when delegation pays, followed by mandatory fresh-context finalization, or says deliver, implement and finalize, or take the slice through review.
日本語の概要は準備中です。原文の説明を表示しています。
Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.
日本語の概要は準備中です。原文の説明を表示しています。
Finalize an implemented rolling-wave slice for user review. Use when the user wants Codex to review the current branch state against a ready-for-review or in-review slice contract, confirm and fix required findings, repeat review and verification until no required findings remain, ask before accepting findings that materially change project shape or contradict project assumptions, record review state, and leave the clean slice in review for complete-slice.
日本語の概要は準備中です。原文の説明を表示しています。
Mark a rolling-wave slice done on explicit user authority, regardless of its current lifecycle status or missing implementation, finalization, review, verification, or child-project state. Use when the user says a slice is done, complete, finished, accepted, or should be marked done; capture available material learnings, update project state, and output roadmap progress without requiring earlier workflow steps.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy the application to production. Only invoke this manually when you are ready to deploy.
日本語の概要は準備中です。原文の説明を表示しています。
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
日本語の概要は準備中です。原文の説明を表示しています。
用户在分析"为什么接受别人小恩惠后无法拒绝大请求""为什么免费试吃会让人买不想买的东西""为什么不好意思拒绝别人的要求"时激活。 典型场景：被免费样品/礼物/帮忙后产生亏欠感、被不请自来的恩惠绑架、面对互惠式让步感到无法说不。 不适用于：正常的朋友间礼尚往来（双方对等）、商业合同的公平交换、无关社交义务的纯技术决策。
日本語の概要は準備中です。原文の説明を表示しています。
[Code Quality] Review an exact pending commit when the commit skill selects lightweight review or the user requests it. --fix-loop repairs and re-reviews; no Git publication authority.
日本語の概要は準備中です。原文の説明を表示しています。
Subagent that scans CopilotKit + AG-UI releases shipped in (and just after) the report window, diffs the git tags to extract what each release actually fixed, and returns a fix-map the weekly-report writer cross-checks against open issues. Catches issues that are quietly already-fixed in a shipped release, and is the authoritative source for the "current release vX.Y.Z" version claims. Invoked by weekly-report (spawned in parallel with the Discord/GitHub pulls); runs as a general-purpose subagent so the orchestrator's context stays small.
日本語の概要は準備中です。原文の説明を表示しています。
Subagent flow for deep-reading GitHub issues + their linked/closing PRs to the bottom. Captures CURRENT state, maintainer status updates, reporter repro, blocking reviewer concerns, hidden second bugs, cross-repo duplicates. Invoked by weekly-report orchestrator; runs as a general-purpose subagent so the orchestrator's context stays small.
日本語の概要は準備中です。原文の説明を表示しています。
Use when applying security best practices — authentication, authorization, CSRF protection, input sanitization, rate limiting, or secure coding — stack-agnostic.
日本語の概要は準備中です。原文の説明を表示しています。
Use when governing a worktree across its whole life — scope-lock declaration, merge-readiness status, scoped verification, and safe cleanup that refuses while unique unmerged commits exist.
日本語の概要は準備中です。原文の説明を表示しています。
Validate whether a feature request fits the existing codebase — check for duplicates, contradictions, scope creep, and architectural misfit
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing production-LLM prompts — few-shot, chain-of-thought, system prompts, templates, self-verification — distinct from prompt-optimizer and refine-prompt.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or editing a rule in src/rules/ — trigger wording, always vs auto classification, size budget — even when the user just says 'add a rule for X'.
日本語の概要は準備中です。原文の説明を表示しています。
Use to run a depth-bounded self-correction loop (attempt → critic verdict → re-attempt) as a tunable test-time compute knob — a do-and-judge specialisation, default off, capability-gated.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a security-maturity scorecard / posture assessment of a module — category ratings with evidence, not a vulnerability hunt. Also on 'wie sicher ist dieses Modul aufgestellt?'
日本語の概要は準備中です。原文の説明を表示しています。
Use when tracing the root cause of a resolved incident or recurring bug — 5-whys chain, fishbone categorisation, contributing-factors split — even if the user says 'why does this keep breaking?'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when shaping a Playwright suite — locator strategy, Page Object boundaries, fixture composition, flake-prevention architecture, CI-vs-local split — even on 'design our E2E tests'.
日本語の概要は準備中です。原文の説明を表示しています。