「returns」の検索結果

Checks compiler/linter errors, deprecation warnings, type errors, failed tests, build config issues. Returns findings with severity, location, effort, recommendations.

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

Checks cyclomatic complexity, nesting, long methods, god classes, method signatures, O(n²), N+1 queries, constants management. Returns findings.

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

Identifies missing tests for critical paths (Money 20+, Security 20+, Data Integrity 15+, Core Flows 15+). Returns list of untested critical business logic with priority justification.

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

Coordinates code quality: ln-511 metrics, ln-512 cleanup, inline agent review (Codex + Gemini), ln-513 regression, ln-514 log analysis. Returns quality_verdict + aggregated results.

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

Checks DRY (10 types), KISS/YAGNI, error handling, DI patterns. Returns findings with severity, location, effort, pattern_signature.

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

Checks unreachable code, unused imports/variables/functions, commented-out code, backward compatibility shims, deprecated patterns. Returns findings.

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

Checks structured logging, health check endpoints, metrics collection, request tracing, log levels. Returns findings with severity, location, effort, recommendations.

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

Checks bootstrap initialization order, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Returns findings.

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

Checks layer leakage in method signatures, missing DTOs, entity leakage to API, inconsistent error contracts. Returns findings with penalty-based scoring.

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

Detects tests that validate framework/library behavior (Prisma, Express, bcrypt, JWT, axios, React hooks) instead of OUR code. Returns findings with REMOVE decisions.

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

Checks hardcoded secrets, SQL injection, XSS, insecure dependencies, missing input validation. Returns findings with severity, location, effort, recommendations.

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

Scans codebase for hardcoded secrets. Returns normalized findings with severity and remediation guidance. Pre-commit hook integration.

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

Compare two local documents and convert differences into LLM-ready Markdown in one synchronous call. Supports PDF, Word, PPT, and image documents accepted by Calliper, and returns a structured markdown diff table suitable for change review, clause comparison, downstream extraction, and rule-based validation.

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

Run the same scrape or task across many accounts at once - each in its own browser profile with its own fingerprint, cookies and exit IP - and read data from sites that need a session or that answer a plain HTTP scraper with a captcha while answering a real browser. One command per site returns JSON, so there are no selectors to write or repair: Amazon and Walmart search, Google and DuckDuckGo results, Reddit posts and comments, X timeline, Medium, Yelp, Indeed job listings, Hacker News, GitHub, PyPI, npm, plus exit-IP and fingerprint checks. Use for multi-account operations you are authorized to run, price and listing monitoring per region, SERP collection, logged-in data, and scrapers that keep breaking. Also for 'scrape amazon', 'google search results', 'reddit data', 'scrape logged in site', 'run task on many accounts', 'site blocks my scraper', 'scraping without selectors'. Node or Python.

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

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.

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

Find question-based Google Autocomplete suggestions for any topic. Prepends question modifiers (what, how, why) to a seed topic and returns real autocomplete suggestions — useful for AEO prompt research, content ideation, and understanding what people ask about a topic. Use when the user wants to discover questions people search for, find content angles, or do keyword/prompt research for a topic.

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

This is the MistEye security gate skill. It is triggered by pre-installation risk checks (including Skill/MCP dependency manifests), pre-access security checks for domains or URLs, IoC malicious detection, and supply-chain risk blocking, especially for common requests such as "take a look at this address/website." It must use `https://app-api.misteye.io/functions/v1/detect`; in dependency and external-link scenarios it has the highest priority. If the API returns `status="malicious"` or any `matches`, the action must be blocked and explicitly reported as "blocked". Only after the first installation is complete should the user be reminded that daily patrols can be enabled with OpenClaw or Hermes (default once per day).

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

Prove — or honestly fail to prove — a specific technical claim: "the fix works", "it's deployed", "the service is running", "the site is done", "there are no vulnerabilities". Atomizes the claim, picks the shortest decisive signal on the evidence ladder, and returns a verdict from a fixed vocabulary (pass / partial / fail / skip) with an explicit coverage boundary. NOT code review, NOT a fix, NOT orchestration — only "what is proven, and what we merely hope". Triggers — "prove it works", "is it really done?", "are you sure?", "we deployed — is it live?", "verify that", "did we actually check?".

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

Route frontend tasks to the right library skill. Detects React/Vue/CSS intent and returns specific skill file paths.

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

Route backend tasks to the right library skill. Detects intent and returns specific skill file paths to load.

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

Route deployment tasks to the right library skill. Detects intent and returns specific platform skill file paths to load.

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

Domain-aware complexity routing: scans the task for domain keywords, matches domain-complexity.csv, and returns complexity level, workflow intensity, and execution tier. Extends Phase 0 orchestration.

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

Domain-aware complexity routing. Scans task description for domain keywords, matches against domain-complexity.csv, returns complexity level, workflow intensity, and execution tier. Extends Phase 0 orchestration.

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

Retrieve up-to-date library, framework, and project documentation using scripts + MCP tools (Context7, Context Hub) with intelligent fallback. Use this skill whenever the user or agent needs documentation for any library, framework, API, SDK, or internal project spec. Triggers on "docs for [X]", "how does [library] work", "find documentation", "API reference for", "look up [feature] in [library]", "latest docs", "what's the API for", "find our [internal spec]", or any request that requires current, accurate documentation rather than relying on training data. Always prefer this skill over raw WebSearch for documentation retrieval — it returns structured, context-efficient results.

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