「security」の検索結果

Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.

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

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

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

Typosquatting detection, install script analysis, dependency confusion prevention, and phantom dependency detection for npm/pip.

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

Pre-push API key and credential scanner - blocks git push if secrets found

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

Payment provider abstraction, webhook security, subscription lifecycle, dunning flows, pricing models, invoicing, tax handling, and refund patterns for SaaS applications.

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

Pre-launch verification across infrastructure, security, legal, payment, email, analytics, and performance. Day-1 monitoring, rollback plan, incident response skeleton, and post-launch week-1 checklist.

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

Release preparation workflow - security audit → E2E tests → review → changelog → docs

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

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.

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

Ethical security testing methodology - 5-phase pipeline, OWASP checklist, proof levels, structured findings

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

Agent arasi iletisim sablonlari. Standard handoff, QA verdict (PASS/FAIL), escalation, bug report, security finding ve status update formatlari.

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

TOCTOU prevention, distributed locking, idempotency keys, race condition detection for Node.js and serverless environments.

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

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

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

Deep behavioral code analysis agent for Bug Hunter. Performs multi-phase scanning to find logic errors, security vulnerabilities, race conditions, and runtime bugs. Uses doc-lookup (Context Hub + Context7) for framework verification. Reports structured JSON findings.

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

Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts. Use whenever the repository has no threat model yet, the architecture changed materially, a security review needs fresh trust-boundary context, or the user explicitly asks for a threat model.

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

Final arbiter for Bug Hunter. Receives Hunter findings and Skeptic challenges, independently re-reads code, and delivers authoritative verdicts with CVSS scoring and proof-of-concept generation for security findings.

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

Write GitHub Actions workflows with proper syntax, reusable workflows, composite actions, matrix builds, caching, and security best practices. Use when creating CI/CD workflows for GitHub-hosted projects or automating GitHub repository tasks.

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

Configure host-based firewalls (iptables, nftables, UFW) and cloud security groups (AWS, GCP, Azure) with practical rules for common scenarios like web servers, databases, and bastion hosts. Use when exposing services, hardening servers, or implementing network segmentation with defense-in-depth strategies.

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

Constructs secure, efficient CI/CD pipelines with supply chain security (SLSA), monorepo optimization, caching strategies, and parallelization patterns for GitHub Actions, GitLab CI, and Argo Workflows. Use when setting up automated testing, building, or deployment workflows.

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

Manage Linux systems covering systemd services, process management, filesystems, networking, performance tuning, and troubleshooting. Use when deploying applications, optimizing server performance, diagnosing production issues, or managing users and security on Linux servers.

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

Implement production-ready service mesh deployments with Istio, Linkerd, or Cilium. Configure mTLS, authorization policies, traffic routing, and progressive delivery patterns for secure, observable microservices. Use when setting up service-to-service communication, implementing zero-trust security, or enabling canary deployments.

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

Implement and maintain compliance with SOC 2, HIPAA, PCI-DSS, and GDPR using unified control mapping, policy-as-code enforcement, and automated evidence collection. Use when building systems requiring regulatory compliance, implementing security controls across multiple frameworks, or automating audit preparation.

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

Diagnose vArmor and Kubernetes security issues involving components, policies, Profiles, webhooks, node enforcers, BehaviorModeling, and NetworkProxy. Use when Pods are Pending, containers exit unexpectedly, policies fail to inject or take effect, policy status is abnormal, node Profiles fail to load, audit events need investigation, or vArmor components are unhealthy. Provide domain context, targeted read-only checks, and evidence interpretation.

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

Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. USE FOR: .NET quality gates in CI; analyzer, coverage, mutation, and architecture-test choices; standardizing `.editorconfig`, `dotnet format`, and warning policy. DO NOT USE FOR: non-.NET repositories; generic CI/CD guidance with no .NET quality stack decisions. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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

Work on WCF services, clients, bindings, contracts, and migration decisions for SOAP and multi-transport service-oriented systems on .NET Framework or compatible stacks. USE FOR: working on WCF services, bindings, or clients; deciding whether a service should stay WCF or move to modern HTTP APIs; reviewing transport, security, or interoperability. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

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