「code analysis」の検索結果

Threat-model a sensitive design with STRIDE on request. Read-only analysis of threats, controls, and implementation constraints.

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

Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and response schema completeness. Produces a polished interactive HTML report with a summary scorecard, site-wide pattern analysis, ranked top issues, and per-endpoint findings with specific fix guidance. Trigger this skill whenever a user provides a documentation URL and asks to audit, review, analyse, or check their API docs. Also trigger for: "do the same audit for X", "audit docs.company.com", "check the API docs at X", "run the API docs audit on X", "review the docs for Y API", or pastes a URL alongside words like audit, review, crawl, check, analyse, quality, completeness, or gaps. Always use this skill — do not attempt the audit without following this structured crawl-score-report workflow.

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

Delegate coding, code review, analysis, and research jobs to Google Antigravity CLI (agy) sub-agents that run alongside your own work. Use this whenever the user asks to spin off, offload, or delegate a task to Antigravity, agy, Gemini, or an "external agent"; wants a second opinion or independent review from a different model; wants intensive repo work (audits, large refactors, research sweeps) run in the background while you keep working; or says things like "have Antigravity do it", "spin up a sub-agent for this", or "get more done in parallel". Also use it proactively when a task is a good fit for parallel delegation and the user has expressed a preference for using Antigravity workers.

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

Use in code_review when the diff touches input handling, auth, queries, files, outbound requests, secrets, dependencies or LLM calls, and in analysis for any new endpoint or data flow

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

This skill should be used when the user sends an image and asks to "analyze this image", "describe this picture", "what's in this image", or any request requiring visual understanding of images. Provides image analysis using Zhipu GLM-4.6V multimodal model.

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

Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.

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

Investigating bugs via root cause analysis, reproduction steps, and impact assessment. Investigation-only — finds why bugs occur and where to fix them, no code. Use when a bug needs RCA before a fix.

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

Enumerating failure modes via pre-mortem analysis. Systematically identifies failure scenarios for plans, designs, and features, scoring them with RPN/AP. Does not write code.

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

Query patent bibliographic (catalog) information from the Nexscope patent database by patent ID or publication number. Triggered when users mention patent bibliographic info queries, patent catalog information, patent applicant queries, patent inventor queries, patent classification codes, patent abstract retrieval, patent citation analysis, patent priority claims, patent application citations, patent examiner information, patent bibliographic data, inventor lookup, applicant lookup, patent classification, patent metadata, Nexscope, or patent citations. Even if the user does not explicitly mention "bibliographic info," this skill should be triggered whenever their need involves querying detailed metadata for a specific patent by patent ID or publication number.

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

Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven. Use when you need exhaustive edge-case analysis of code, specs, or diffs.

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

Diagnose and fix mini-program failures through reproducible, evidence-driven root-cause analysis across source, state, asynchronous timing, caches, mock data, build versions, platform behavior, devices, cloud calls, and external services. Use when users report white screens, crashes, stale or jumping values, missing data, intermittent behavior, permission failures, performance stalls, device-only defects, API or cloud-function errors, source-versus-build mismatches, or regressions whose cause is not yet established. Freezes the observation environment, ranks competing hypotheses, runs discriminating checks, creates a failing regression test before repair, covers analogous states, and never hides a known failure with longer waits, swallowed errors, forced success, or cosmetic patches.

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

Use for Korean (Hangul) fan translations of retro console or PC games, including ROM or disc analysis, text-engine reverse engineering, Hangul fonts and custom encodings, script extraction and reinsertion, code hooks, reproducible product builds, and emulator verification. Apply it to new investigations and follow-up work in existing Korean-patch projects. 레트로 게임 한글화·한글패치·한글 패치·ROM 번역의 신규 조사와 기존 프로젝트 후속 작업에 사용한다.

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

竞品深度扫描与早期付费客户证据研究；输出行业画像假设和可验收需求交接。批量抓取对手落地页（title/h1/intro/pricing）、定价页、博客 top 10、 变更历史（Wayback）。底层调 actionbook（并发 30 tab + 省 90% token）。 当用户说"分析对手"、"看看竞品在做啥"、"找对标"、"扫一下 top 10"时调用。

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

Generate first-draft technical documentation from code analysis

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

Use when the user wants a cited, structured read of local documents and project knowledge. Triggers on: "analyze these docs", "scan my project for context", "read the docs folder", "summarize what's in .beagle/concepts/", "extract context from docs/", "what's in this folder", "go read everything in X and tell me what's there". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), web research (use web-research), LLM-as-judge evaluation (use llm-judge), or document editing (use humanize-beagle). Produces a written scan plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.

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

Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.

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

Entity-aware code change analysis using the pi-sem tools. Use when the user asks what changed, wants blast radius or affected tests, needs focused context for a function/class, wants review help on a commit/branch/PR, or asks to compare semantic diff with raw git diff. Prefer sem_context and sem_impact; use sem_diff selectively for summaries and reviews.

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

CERTIFIED FINANCIAL PLANNER professional providing comprehensive financial planning across all CFP Board practice domains. Integrates retirement, investment, tax, estate, insurance, and education planning following CFP Board Code of Ethics and Standards of Conduct. Use for holistic financial plans, cash flow analysis, net worth statements, insurance needs, estate planning coordination, education funding (529 plans), tax strategies, retirement projections, or CFP Board Practice Standards compliance.

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

Grammar and syntactic structures across human languages -- word order typology (SVO, SOV, VSO, VOS, OVS, OSV), morphological systems (isolating, agglutinative, fusional, polysynthetic), agreement patterns (gender, number, case, person), phrase structure, clause embedding, and cross-linguistic universals. Covers constituent analysis, dependency vs. constituency grammars, grammatical relations (subject, object, oblique), ergativity vs. accusativity, tense-aspect-mood systems, and how grammar encodes meaning differently across language families. Use when analyzing sentence structure, comparing grammar systems, teaching grammatical concepts, or understanding why a learner makes transfer errors from their L1.

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

clj-kondo linter with Gay.jl 3-color integration for GF(3) conservation in Clojure code analysis.

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

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

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

Systematic process for analyzing and modernizing legacy applications to comply with the 12-Factor App methodology. Covers code analysis, configuration externalization, dependency management, and container/Kubernetes best practices.

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

Analysis criteria, transformation patterns, output format, and validation checklist for refactoring Claude Code agent prompt files. Load this skill when preparing to run the subagent-refactorer agent or when reviewing agent prompt files for structural, model optimization, or instruction quality improvements.

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

Autonomous feature research and gap analysis. Use when starting /add-new-feature or analyzing existing architecture documents. Explores codebase patterns, identifies ambiguities, and produces feature-context-{slug}.md for orchestrator RT-ICA phase. Does NOT make technical decisions.

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