「by」の検索結果

Use ast-grep (sg) for AST-aware code search and rewrite across 25 languages. Trigger for structural code matching or deterministic codemods: find every function/call/class/import shaped like X, rewrite console.log to logger.info, strip `as any`, migrate require() to import, find empty catch blocks or missing await, and scan/apply YAML rules. Prefer this over rg/grep when the target is syntax shape rather than text; use rg for string contents, comments, filenames, or regex-style byte searches.

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

Use this skill whenever the user asks to inspect, audit, review, assess, or evaluate a codebase/project for maintainability, extensibility, architecture, reliability, security, testing, engineering quality, or AI-agent/prompt/tooling risks. Also use this when invoked by `/inspect`. It performs a read-only, evidence-backed, multi-agent project inspection with complete file coverage, per-dimension scoring, blunt technical findings, and explicit degraded-mode disclosure.

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

By political reporter Erin Handley and staff Topic: Cyber Security Posted Thu 24 Sep 2026 at 6:31am

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

Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.

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

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

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

Use when you need code research over an indexed codebase with minimal context: structural graph queries (who calls X, call chains, architecture overview, dead code, cross-service HTTP routes) instead of file-by-file grep/read cycles. Also trigger to minimise token spend on repetitive code exploration.

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

Optimize and convert Zenn Flavored Markdown (ZFM) articles to Dev.to (Forem) compatible Markdown. Use this skill whenever the user wants to post a Zenn article to Dev.to, needs to convert markdown for cross-posting, or asks to "optimize for dev.to". It handles front matter conversion, Liquid tag embeds, KaTeX math blocks, callout transformations, and general formatting adjustments required by Dev.to.

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

Search Grants.gov for federal funding opportunities by agency, category, and eligibility. 4 tools.

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

You are a code education expert specializing in explaining complex code through clear narratives, visual diagrams, and step-by-step breakdowns. Transform difficult concepts into understandable expl...

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

Generates B2B/B2C leads by scraping Google Maps, websites, Instagram, TikTok, Facebook, LinkedIn, YouTube, and Google Search. Use when user asks to find leads, prospects, businesses, build lead lis...

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

Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...

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

Act as FriendlyBet's CEO and primary front door for every FriendlyBet request through automatic company preflight. Own end-to-end routing, planning, execution coordination, department orchestration, decision-rights enforcement, quality gates, board-style reporting, and escalation only for strategic, legal, brand, cost, risk, or taste decisions. Use by default in FriendlyBet threads, with full department planning for broad, ambiguous, strategic, cross-functional, or outcome-driven requests such as SEO, new features, multi-sport expansion, product direction, release execution, company operations, or agent coordination.

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

Derive slices from specs, order by dependencies, write acceptance criteria with citations, and finalize phase/progress artifacts

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

Present and apply contradiction fixes one-by-one, flag assumptions, run consistency checks, and write propagation record

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

Layer-by-layer remediation loop using adversarial audits, targeted fixes, and fresh-run verification enforcement

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

Axis-by-axis interview methodology for establishing engineering performance budgets during architecture PRD compilation. Use when conducting the Step 10.5 performance budget interview in /create-prd-compile.

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

Cross-session progress tracking, pattern extraction, and session resumption. Gives agents memory across sessions using markdown files in `.memory/pipeline/progress/`. Subsumes self-improving-agent — handles both implementation tracking AND experiential learning in one skill. Workflows invoke specific protocols by name.

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

Introduce genuinely new scope into the pipeline by classifying change type and cascading updates through downstream layers

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

Execute ambiguity audit document-by-document with implementer simulation, rubric scoring, cross-layer checks, remediation, and verdicting

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

Utility — fill the surface stack map in tech-stack.md and provision skills using intelligent resolution. Called by pipeline commands when tech stack info changes.

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

Enables ultra-granular, line-by-line code analysis to build deep architectural context before vulnerability or bug finding.

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

Step-by-step onboarding guide for setting up a new AI Personal Assistant on OpenClaw. Use when: a new PA is being created, someone asks how to set up an agent, or guiding a user through the full setup process from account creation to first response.

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

Step-by-step setup and troubleshooting for connecting an owner's Google Calendar to an OpenClaw agent with read and write access. Use when: setting up calendar access for the first time, fixing read-only access, re-authenticating a broken Google connection, explaining the difference between the owner's Google account and the agent's Google account, how an OpenClaw agent accesses Gmail or Google Workspace, where credentials are stored, how to use the agent inbox, how to give the agent write access to the owner's calendar, or guiding another agent or user through the email or calendar setup model.

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

Schedule meetings, parse meeting notes, extract action items. Three distinct intents covered. Invoke when user mentions a specific meeting (past or future) by name or context. NOT for general calendar checks (use direct calendar.py), NOT for time-zone math. Triggers: "schedule with X", "minutes of the X meeting", "action items from yesterday's meeting", "prep me for meeting with X".

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