「fix」の検索結果

Adversarial "perfection" review — hold a change to an *ideal* bar, not just a correct one, assuming eternal time, unlimited energy, and no ship pressure. Use when the user asks to review "for perfection", to make a defect "impossible to express", or to hunt where a defect "relocates" across review rounds. Grounds every claim in the diff, fans out adversarial verifiers via Workflow, and reports residual surfaces with a structural fix for each. ONLY invoke when the user explicitly asks for a perfection / ideal-bar review.

日本語の概要は準備中です。原文の説明を表示しています。

Author, lint, and publish skill packages that satisfy the library authoring standard. Use when creating a new skill, reviewing a skill PR, or fixing one that never activates.

日本語の概要は準備中です。原文の説明を表示しています。

Design tokens, light/dark theming, and WCAG contrast validation for HTML documents and decks, compiled into one inlinable CSS bundle. Use when theming a report or deck, auditing contrast, or fixing dark-mode color drift.

日本語の概要は準備中です。原文の説明を表示しています。

Transform AI-generated content into human-sounding writing via AI pattern detection, rhythm restoration, and authenticity scoring. Use when content sounds robotic, uses AI cliches, or the user wants to humanize or fix AI writing.

日本語の概要は準備中です。原文の説明を表示しています。

End-to-end testing with Playwright: test generation, page objects, locator strategy, flaky- test diagnosis, visual regression, and CI integration. Use when writing E2E tests, fixing flaky tests, or migrating from Cypress/Selenium.

日本語の概要は準備中です。原文の説明を表示しています。

Systematic root-cause debugging. Iron Law: no fixes without root cause investigation first. Four phases: Root Cause Investigation, Pattern Analysis (6 known patterns), Hypothesis Testing (3-strike rule), Implementation. Structured debug report output.

日本語の概要は準備中です。原文の説明を表示しています。

Writes E2E tests with Playwright including test scripts, page objects, test fixtures, reporters, CI integration, API mocking, and visual regression testing.

日本語の概要は準備中です。原文の説明を表示しています。

Clean AI slop from code with certainty-based findings and auto-fixes

日本語の概要は準備中です。原文の説明を表示しています。

Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`, when a test fails with missing environment variables, or when diagnosing a failing or suspiciously passing acceptance test.

日本語の概要は準備中です。原文の説明を表示しています。

Technical SEO reference for deep fixes: Web Vitals, JS SEO, migrations, schema. "plan a site migration"

日本語の概要は準備中です。原文の説明を表示しています。

Analyze the SEO of one URL, scored /80 with paste-ready fixes. "analyze the SEO of this page"

日本語の概要は準備中です。原文の説明を表示しています。

Create, audit and fix URL redirects on a connected CMS, approval-gated. "set up a 301 redirect"

日本語の概要は準備中です。原文の説明を表示しています。

Score one piece via eval-runner on six dimensions with a fix list. Many pieces → eval-suite. "score this draft before it ships"

日本語の概要は準備中です。原文の説明を表示しています。

Validate hreflang, alternate-language link tags and x-default from pasted HTML or sitemaps, with fixes. "check our hreflang tags"

日本語の概要は準備中です。原文の説明を表示しています。

Plan CRO for pages, forms and checkout with ICE-ranked fixes. One page → landing-page-audit. "reduce cart abandonment"

日本語の概要は準備中です。原文の説明を表示しています。

Show help with live plugin counts: getting started, which skill fits a goal, fixes. "what can this plugin do"

日本語の概要は準備中です。原文の説明を表示しています。

安全诊断并修复 ESLint error、warning 和配置兼容问题。用于用户要求运行 lint、解释 ESLint 报错、限定范围自动修复或迁移 ESLint 配置时；优先使用项目锁定的包管理器与版本，先预检再修改，不自动下载最新版或批量改写无关源码。

日本語の概要は準備中です。原文の説明を表示しています。

Search an Agent Relay workspace's shared coding-agent sessions for prior work, decisions, fixes, or the context behind a task or pull request. Use when team history could answer the user's question or prevent repeating an investigation.

日本語の概要は準備中です。原文の説明を表示しています。

Use when creating or fixing .claude/rules/ files - provides correct paths frontmatter (not globs), glob patterns, and avoids Cursor-specific fields like alwaysApply

日本語の概要は準備中です。原文の説明を表示しています。

Automatic final verification pass on completed deliverables. Runs at the end of every fable-mode run — those skills invoke it before delivery. Also triggers when the user says "double check this". Uses a panel of fresh checker agents when spawning is authorized (otherwise a cold self-check) to verify the finished output — not to redo the task. Any FAIL gets fixed and re-checked before delivery.

日本語の概要は準備中です。原文の説明を表示しています。

Pick the right LLM for LEGAL TRANSLATION — translating contracts, statutes, case law, and legal correspondence across languages, including Arabic/MENA. Vendor-neutral routing triangulated from mid-2026 evidence (WMT25 human eval, SwiLTra-Bench legal-MT, multilingual-reasoning proxies, ArabLegalEval). There is NO clean legal-translation leaderboard, so this vertical is directional and treats human legal-linguist review as mandatory. Asks up to 4 quick questions (language pair, cost, speed, privacy/certification), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model to translate this contract/statute", "best AI for legal translation", "translate this legal doc to/from Arabic", or is about to machine-translate legal text without a fixed model.

日本語の概要は準備中です。原文の説明を表示しています。

Pick the right LLM for CONTRACT DRAFTING — generating, redlining, or rewriting contract language from instructions. Vendor-neutral routing grounded in mid-2026 legal benchmarks (legalbenchmarks.ai Contract Drafting). Asks up to 4 quick questions (cost, speed, accuracy/ stakes, privacy/jurisdiction/language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model should I use to draft this clause/agreement", "best AI for drafting contracts", "route this drafting task", or is about to generate/redline contract text and hasn't fixed a model.

日本語の概要は準備中です。原文の説明を表示しています。

Pick the right LLM for CONTRACT REVIEW — reviewing an existing agreement for risk, deviations from standard, missing protections, and internal contradictions, and proposing redlines. Vendor-neutral routing grounded in mid-2026 legal benchmarks. Contract review is a COMPOSITE skill (extraction + reasoning + redlining + conflict-detection), so this routes by the dominant sub-task. Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/ language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model to review this contract / NDA / MSA", "best AI to redline", "route this contract review", or is about to review an agreement without a fixed model.

日本語の概要は準備中です。原文の説明を表示しています。

Pick the right LLM for LEGAL INFO EXTRACTION — pulling facts, clauses, dates, parties, obligations, and structured fields out of contracts and legal documents. Vendor-neutral routing grounded in mid-2026 benchmarks (legalbenchmarks.ai Info Extraction; CUAD/MAUD/ACORD). Asks up to 4 quick questions (cost, speed, accuracy/stakes, privacy/jurisdiction/language), then recommends a primary model + fallback + what to avoid + what a human must verify. Use when someone asks "which model should I use to extract clauses/data from these documents", "best AI for contract data extraction", "route this extraction task", or is about to pull structured fields from legal docs without a fixed model.

日本語の概要は準備中です。原文の説明を表示しています。