4,425 件 ・ 関連度順
概要と使いどころ
Use when working with Semgrep — semgrep static application security testing (SAST). Covers code scanning, custom rule creation, CI integration, autofix capabilities, multi-language support, and vulnerability triage. Use when scanning source code for security vulnerabilities, creating custom detection rules, or integrating SAST into CI pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Snyk — snyk security scanning and vulnerability analysis. Covers dependency vulnerability scanning, container image scanning, IaC security scanning, code analysis, license compliance, and fix recommendations. Use when scanning for vulnerabilities, analyzing dependency risks, reviewing container security, or auditing IaC configurations.
日本語の概要は準備中です。原文の説明を表示しています。
4-phase root cause debugging: understand bugs before fixing.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-commit review: security scan, quality gates, auto-fix.
日本語の概要は準備中です。原文の説明を表示しています。
Security scan + code quality + auto-fix on git push.
日本語の概要は準備中です。原文の説明を表示しています。
Use when internet_learner cycles all report rejected.
日本語の概要は準備中です。原文の説明を表示しています。
Use for autonomous bug-hunt: scan, reproduce, fix, bounty.
日本語の概要は準備中です。原文の説明を表示しています。
Recent Updates - Devin Docs — Vor 2 Tagen · The latest Devin updates: recently released features, improvements, and bug fixes across the product, upda
日本語の概要は準備中です。原文の説明を表示しています。
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Visual inspection of live websites to find and fix design issues. Use when reviewing UI layout/design, checking responsive design visually, detecting visual inconsistencies, or diagnosing CSS/accessibility problems at the source code level. Not for automated E2E testing.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".
日本語の概要は準備中です。原文の説明を表示しています。
Create and manage Netlify deploys — Git continuous deployment, CLI manual/anonymous deploys, Deploy to Netlify buttons, drag-and-drop, and per-context netlify.toml build settings. Use when linking a repo, deploying from the CLI, setting up Deploy Previews or branch deploys, configuring deploy contexts, adding skew protection, fixing a failed or secrets-flagged deploy, or wiring build hooks and Deploy to Netlify buttons.
日本語の概要は準備中です。原文の説明を表示しています。
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query writing unless user asks for performance or index help. Prefer indexing as optimization strategy. Use MongoDB MCP when available.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
日本語の概要は準備中です。原文の説明を表示しています。
Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't build or run, or otherwise work with `hf spaces …`, `@spaces.GPU`, Space README frontmatter, or the `spaces` Python package.
日本語の概要は準備中です。原文の説明を表示しています。
Use multiple Claude agents to investigate and fix independent problems concurrently
日本語の概要は準備中です。原文の説明を表示しています。
Scope the real change surface before editing. Use when planning a feature, bugfix, refactor, or review and you need a concrete map of likely touch points, dependencies, tests, and nearby risks.
日本語の概要は準備中です。原文の説明を表示しています。
Review a diff for clarity and safe simplifications, then optionally apply low-risk fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose devcontainer configuration problems and guide development environment setup. This skill should be used when the user asks to 'set up devcontainer', 'fix container startup', 'configure VS Code dev container', 'Codespaces setup', or has Docker development environment issues. Keywords: devcontainer, docker, VS Code, Codespaces, container, development environment, Dockerfile.
日本語の概要は準備中です。原文の説明を表示しています。
Make .NET projects compatible with Native AOT and trimming by systematically resolving IL trim/AOT analyzer warnings. USE FOR: making projects AOT-compatible, fixing trimming warnings, resolving IL warnings (IL2026, IL2070, IL2067, IL2072, IL3050), adding DynamicallyAccessedMembers annotations, enabling IsAotCompatible. DO NOT USE FOR: publishing native AOT binaries, optimizing binary size, replacing reflection-heavy libraries with alternatives. INVOKES: no tools — pure knowledge skill.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate a .NET 10 project or solution to .NET 11 and resolve all breaking changes. This is a MIGRATION skill — use it when upgrading from .NET 10 to .NET 11, NOT for writing new programs. USE FOR: upgrading TargetFramework from net10.0 to net11.0, fixing build errors after updating the .NET 11 SDK, resolving source-breaking and behavioral changes in .NET 11 runtime, C# 15 compiler, and EF Core 11, adapting to updated minimum hardware requirements (x86-64-v2, Arm64 LSE), and updating CI/CD pipelines and Dockerfiles for .NET 11. DO NOT USE FOR: .NET Framework migrations, upgrading from .NET 9 or earlier, greenfield .NET 11 projects, or cosmetic modernization unrelated to the upgrade. NOTE: .NET 11 is in preview. Covers breaking changes through Preview 3.
日本語の概要は準備中です。原文の説明を表示しています。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
日本語の概要は準備中です。原文の説明を表示しています。
Catalog of MSBuild anti-patterns with detection rules and fix recipes. Only activate in MSBuild/.NET build context. USE FOR: reviewing, auditing, or cleaning up .csproj, .vbproj, .fsproj, .props, .targets, or .proj files. Each anti-pattern has a symptom, explanation, and concrete BAD→GOOD transformation. Covers Exec-instead-of-built-in-task, unquoted conditions, hardcoded paths, restating SDK defaults, scattered package versions, and more. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake, etc.), project migration to SDK-style (use msbuild-modernization).
日本語の概要は準備中です。原文の説明を表示しています。
[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res
日本語の概要は準備中です。原文の説明を表示しています。