テスト・セキュリティのスキル

Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → use the add-docs flow; only linting/formatting Markdown → run `uv run invoke docs.lint`.

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

Implements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet → opsmill-dev-test-driving-bugs; still diagnosing, or asked to fix a bug with no analysis or reproduction test yet → opsmill-dev-analyzing-bugs.

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

Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.

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

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

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

Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the idea is already turned into a spec or PRD; bug fixes or refactors; the idea is hardened and you are ready to write the PRD → creating-prd.

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

Performs root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written. TRIGGER when: triaging or diagnosing a bug, investigating why something misbehaves, an issue number/URL handed over for analysis, needing the root cause before touching code. DO NOT TRIGGER when: a failing reproduction test already exists and you are ready to fix → opsmill-dev-fixing-bugs; writing that reproduction test → opsmill-dev-test-driving-bugs; capturing a new bug as a ticket → opsmill-dev-creating-issues.

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

Test-driven development workflow with philosophy guide - plan → write tests → implement → validate

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

Abonelik fiyatlama stratejileri. 3-tier framework, price anchoring, charm pricing, regional pricing (18 ulke), introductory offers, win-back campaigns, churn prevention ve A/B testing methodology.

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

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

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

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

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

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

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

SOC2 Type II compliance - Trust Service Criteria, access controls, audit logging, change management, incident response, evidence collection

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

Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.

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

Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.

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

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

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

Comprehensive testing workflow - unit tests ∥ integration tests → E2E tests

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

Test pyramid decision matrix, coverage targets, when to write which test type, mock vs real dependency decisions, and test ROI analysis.

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

Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.

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

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.

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

Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.

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

Formal theorem proving with research, testing, and verification phases

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

Self-healing codebase system. Monitors runtime errors, test failures, and build breaks. Automatically diagnoses root cause, generates fix, validates fix, and applies if safe. Zero human intervention for routine failures.

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

Security audit workflow - OWASP Top 10, input validation, auth, secret detection, vulnerability scan

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

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

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