「unsafe」の検索結果

Takes a skill — a .skill or .zip archive, a bare SKILL.md, a folder, or just a raw idea — and produces a package ready for public distribution on lawve.ai, plus the exact entries for the submission form. Runs a gate first: skills with no plausible legal use, unsafe code, or licensing bars are declined with reasons, and general-purpose skills that could serve legal work are offered a legal adaptation instead. Then applies the standard compliance transforms — structure, metadata, attribution, dependency ladders, orphaned-file repair, limitations disclosure — validates the result, and delivers a zip. Raw ideas are gated first, built (via skill-creator where available), then adapted. Use for "make this Lawve-compliant," "prep this skill for Lawve," "package for lawve.ai," "is this suitable for Lawve," "get my skill ready to publish," or any request to ready a skill for the Lawve catalogue.

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

Secure Python services against secret leakage, injection, unsafe subprocess calls, and dependency drift. Use when handling env vars, tokens, SQL, file paths, shell commands, auth flows, or Python security gates.

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

Audit GitHub Actions that run AI agents for prompt injection, unsafe interpolation, sandbox gaps, and permissive actor rules. Use for agentic CI workflows, not general application code review.

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

Scan .claude/ directory for security misconfigurations, exposed secrets, unsafe permissions

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

Use when you need to apply Java secure coding best practices — including validating untrusted inputs, defending against injection attacks with parameterized queries, minimizing attack surface via least privilege, applying strong cryptographic algorithms, handling exceptions securely without exposing sensitive data, managing secrets at runtime, avoiding unsafe deserialization, and encoding output to prevent XSS. This should trigger for requests such as Review Java code for secure coding; Find input validation risks in Java code; Review Java code for injection vulnerabilities; Improve secure error handling in Java services; Harden Java code against common security flaws. Part of Plinth Toolkit

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

Add or revise source-level Rustdoc for Shift Rust APIs. Use before writing or editing documentation comments in `.rs` files, especially for public or crate-visible APIs, domain structures, compiler adapters, persistence boundaries, trait implementations, unsafe code, or any API where ownership, units, coordinate spaces, mutation, I/O, sparse behavior, failure modes, panics, or concurrency are easy to misunderstand.

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

Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.

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

Fix Riverpod "Using ref when widget is unmounted is unsafe" error in ConsumerStatefulWidget. Use when: (1) Error thrown in dispose() when calling ref.read(), (2) Need to call a service method during widget cleanup, (3) ConsumerStatefulWidget needs to perform actions on provider when user navigates away. Solution: cache the service/notifier in initState with late final.

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

Analyze vulnerable code to identify underlying root causes such as violated assumptions, incorrect invariants, missing validation checks, or unsafe component interactions. Use when investigating security vulnerabilities, CVEs, exploit code, or security audit findings. Infers why the vulnerability exists beyond surface symptoms, identifies systemic issues, and explains the chain of failures that enable exploitation.

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

Statically analyze code to detect security vulnerabilities including buffer overflows, injection risks (SQL, command, XSS), insecure deserialization, improper authentication, hard-coded credentials, and unsafe cryptography. Use when: (1) Performing security code review, (2) Analyzing code for OWASP Top 10 vulnerabilities, (3) Identifying CWE-classified weaknesses, (4) Generating security audit reports, (5) Reviewing code before deployment, or (6) Assessing third-party code security. Findings categorized by CWE ID and severity (Critical/High/Medium/Low).

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

Proposes secure remediation strategies for detected security vulnerabilities including buffer overflows, injection risks, insecure deserialization, improper authentication, and unsafe cryptographic usage. Provides recommended security checks, safer API alternatives, design-level changes, code examples, trade-off analysis, and prioritized remediation plans. Does NOT automatically modify code unless explicitly requested.

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

Design and validate model-facing tool definitions with clear names, action-oriented descriptions, bounded JSON Schema parameters, explicit side effects, safe defaults, idempotency, errors, and realistic tests. Use when creating function-calling tools, MCP tools, agent actions, structured tool inputs, or when a model selects the wrong tool, invents arguments, or causes unsafe side effects.

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

Think and work like an expert FPGA Engineer. Use when a task calls for FPGA Engineer judgment. Reasons from metastability budgets, setup/hold margins, and tool-reported WNS/TNS through Vivado/Quartus timing and CDC reports, XDC/SDC constraints, Spyglass/Verilator lint, and ILA/IBERT lab bring-up while treating unsafe clock-domain crossings, reset domain crossings, sim-versus-silicon X mismatches, and unconstrained timing paths as first-class failure modes.

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

Use when the diff builds a query, a shell command or argv, a subprocess environment, a template, an XML parse, an eval or a deserialization from data that may be attacker-controlled - SQL/NoSQL, OS command, argument, env-var, template and code injection, XXE, unsafe deserialization

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

Use before and after calling rollback_release - what a rollback restores per delivery mode, when a schema change makes a code rollback unsafe, how to work and report manual_steps, and what to do when rollback_release refuses

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

Use when changing the database schema - detect the repo's migration tool, ship a new migration in its layout, never edit an applied one, and avoid lock-unsafe DDL on a live table

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

Use when writing React + TypeScript components - functional components, explicit typed props, derived state over effects, and no any/unsafe casts

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

Threat-models and hardens an application, API, data flow, dependency, or deployment against authentication and authorization flaws, injection, secrets exposure, unsafe deserialization, SSRF, abuse, privacy loss, and supply-chain risk. Use for security review, threat modeling, hardening, or sensitive changes. Not for generic code style review or an unexplained bug without a security hypothesis.

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

Reviews Rust FFI code for type safety, memory layout compatibility, string handling, callback patterns, and unsafe boundary correctness. Use when reviewing extern blocks, #[repr(C)] types, bindgen output, or code calling C/C++ libraries.

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

Reviews Rust code for ownership, borrowing, lifetime, error handling, trait design, unsafe usage, and common mistakes. Use when reviewing .rs files, checking borrow checker issues, error handling patterns, or trait implementations. Covers Rust 2024 edition patterns and modern idioms.

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

Review a change for security defects such as secret exposure, injection, authentication/authorization failures, unsafe deserialization, and dependency risk. Use for an independent security perspective on a defined change set.

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

Rust development intelligence. 14 domains, 11 stacks, 300+ entries. Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check Rust code. Domains: pattern, crate, error, perf, test, concurrency, traits, arch, idiom, anti, tooling, module, unsafe. Stacks: web-axum, web-actix, web-rocket, web-warp, cli, grpc, database, async-runtime, auth, wasm, embedded. Integrations: arch_system generator.

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

Add a runtime guard that evaluates agent actions, blocks dangerous commands or secret exposure, and audits new skills before they run.

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

Use CC Safety Net when coding-agent CLIs need pre-execution hooks that block destructive commands, secret access, and unsafe file operations before tools run.

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