테스트·보안 스킬

Drafts U.S. commercial real estate access and indemnity (right-of-entry) agreements for pre-closing due diligence. Covers license grants, non-invasive vs invasive testing gates, insurance/endorsement requirements, indemnity with discovery carve-outs, restoration and lien remedies, confidentiality, and anti-indemnity guardrails. Trigger: access agreement, right of entry, due diligence access, Phase I/II, invasive testing, pre-PSA site inspection.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards. USE THIS SKILL WHEN: - You need to review or audit actuarial models (reserving, pricing, capital) - Someone asks about loss triangle analysis or reserve adequacy - You are evaluating IBNR calculations, chain ladder methods, or Bornhuetter-Ferguson - A project involves insurance pricing, GLM rating models, or ratemaking - You need to assess Solvency II SCR calculations or RBC compliance - Someone mentions actuarial opinions, ASOP compliance, or SOA standards - You are reviewing stochastic models, ESG configurations, or DFA frameworks - A codebase uses actuarial libraries (chainladder, lifetables, ChainLadder R package) TRIGGER PHRASES: "actuarial", "loss reserving", "IBNR", "chain ladder", "premium pricing", "mortality table", "Solvency II", "capital adequacy", "ratemaking", "GLM pricing", "risk-based capital", "reserve analysis", "actuarial opinion"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs Fable 5 and OpenAI Codex as co-founders on the Rocket Fuel operating system. Fable is the Visionary (vision, plan, standards, final review); Codex is the Integrator (filters the plan, executes the build, reports). Context-routed, one entry point, four functions: KICKOFF a new project, CLARITY BREAK to refactor an existing one, SAME PAGE MEETING to pressure-test a plan, BUILD A ROCK to hand Codex a scoped task. Use when the user says /rocket-fuel, wants to start or refactor a project with Codex, wants a plan reviewed by a second model, or wants to delegate a build to Codex.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Technische, inhaltliche und internationale SEO-Probleme für Deutschland und den DACH-Raum prüfen und priorisieren. Nutze diesen Skill bei Ranking- oder Trafficeinbrüchen, bei Problemen mit Crawling, Indexierung, Rendering, Canonicals, Weiterleitungen, Ladezeit, interner Verlinkung, hreflang oder lokaler Sichtbarkeit, vor und nach Migrationen und Relaunches, und wenn Befunde aus der Search Console eingeordnet werden sollen. Liefert reproduzierbare Evidenz statt Vermutungen, trennt Beobachtung von Hypothese und bleibt lesend: produktive Änderungen brauchen eine gesonderte Freigabe.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when upgrading an existing Spring Boot application, for example from Boot 3.x to Boot 4 or to the latest Spring Boot and Java: dependency transitions and starter renames, test annotations such as @MockBean to @MockitoBean, Jackson 3 issues, Spring Modulith 2 or Testcontainers 2 upgrades, code that stops compiling after a version bump, or planning a phased migration. Not for greenfield project creation or isolated repository design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deeply scope a problem before coding: parallel Explore agents map related files, similar implementations, and test patterns, producing a problem definition, boundaries, and minimal implementation plan. Use when planning a feature, investigating a bug, or entering an unfamiliar codebase area.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verify Claude, Codex, and Grok availability plus Director guidance, relay, agents, and skills. Audit optional hooks only when selected. Use after installation or when a native surface misbehaves.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

後方互換性がゴミコードを量産する構造を検出し、互換性を「契約と撤去計画」として管理する ガバナンスを支援するスキル。公開API境界の明確化、非推奨化サイクル（deprecation cycle）の 制度化、互換層の局所化（Adapter/Strangler Fig）、契約テスト（CDC）による互換性検証、 AI生成コードの互換性ゲート設計を含む。コードレビュー、API設計、リファクタリング、 レガシー移行時に互換性起因の技術的負債を防ぐために使用。 対象言語: 言語非依存（Java, TypeScript, Go, Python, Rust等すべて）。 トリガー：「後方互換性を保ちたい」「非推奨APIをどうする」「互換層が増えてきた」 「レガシー移行の戦略」「API設計レビュー」「互換性のためのコードが多い」 「deprecation policyを作りたい」「破壊的変更の管理」といった互換性管理関連リクエストで起動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ソフトウェアにおける非正常状態（Error, Defect, Fault, Failure）の分類と定義を提供する。 JIS規格・JSTQB・Bertrand Meyer等の複数の標準に基づき、各概念の違いを明確化し、 適切なエラー設計・障害対策の判断を支援する。エラー設計、障害分析、コードレビュー、 テスト設計時に用語の混乱を防ぎ、正確な分類に基づく対処戦略の選択に使用。 対象言語: 言語非依存。 トリガー：「ErrorとFaultの違い」「DefectとBugの関係」「障害と故障の区別」 「エラーの分類」「Failureとは何か」「非正常状態の設計」「エラー用語の定義」 「エラーと欠陥の違い」「faultとfailureの違い」 といったエラー分類・用語定義関連リクエストで起動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Pull Request をグリーンにするスキル。CI チェックの失敗解消と、PR に紐づく Issue の 修正・クローズを一括で実行する。GitHub Actions の CI ログ分析、ローカル CI （`./scripts/ci-check.sh`）の実行、エラーの根本原因特定と修正、PR コメントや リンクされた Issue の解消を含む。解消した Issue は確認後にクローズする。 ループモード（`/loop 5 /pr-green`）にも対応し、自律的に CI 監視・修正・プッシュを繰り返す。 トリガー：「PR をグリーンにして」「CI を通して」「CI エラーを直して」 「PR の issue を解消して」「PR を修正して」「CI が落ちている」「テストが失敗している」 「PR のレビュー指摘を直して」「PR を mergeable にして」 といった PR 修正・CI 解消関連リクエストで起動。PR 番号が指定されなくても、 現在のブランチから自動検出して対応する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ドメインモデル中心の開発手順ガイド。テストファーストでドメインモデルを設計・実装し、 インメモリリポジトリ→ユースケース→インフラの順で開発を進める手法を解説。 トリガー：「ドメインモデルから始めたい」「TDDでDDD」「インメモリリポジトリの作り方」 「ユースケースのテスト方法」「DDD開発の進め方」等の開発プロセス関連リクエストで起動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

5-phase migration process, security guardrails, deliverables, archival protocol, and the 10-item completion checklist for any CI/CD migration to GitHub Actions. Load at the start of every migration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Codify project review rules as deterministic guards — ast-grep structural rules (with TDD-style rule tests) for mechanical checks, REVIEW_GUIDELINES.md for qualitative ones, wired into the project gate / wf verify. Use when the user wants to define review rules, turn a repeated review finding into a lint/guard, or set up ast-grep in a project.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates audit trail infrastructure for entities. Implements IAuditable interface, EF Core SaveChanges interceptor, and automatic population of CreatedAt, UpdatedAt, CreatedBy, and UpdatedBy fields.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures integration tests with WebApplicationFactory and Testcontainers. Provides test database setup, authentication helpers, and utilities for testing API endpoints with real dependencies.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generates unit tests for command and query handlers using xUnit and NSubstitute. Implements Arrange-Act-Assert pattern with comprehensive test coverage for success and failure scenarios.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Skill for writing and running tests for ActonOS. Covers unit tests, integration tests, test patterns, mocking, and coverage.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Synthetic stakeholder panel — build a mixed panel of grounded personas, run independent and cross-reaction rounds against a launch, pricing change, PRD, or message, and return ranked objections and messages to test. Use when asked to "simulate how users will react", "test this launch with a synthetic panel", "focus group this", "how will people react to this pricing change", or "pressure-test this message".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Security-focused review for Hyperlane protocol code. Use for Solidity contracts, Rust agents, and infrastructure changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encode and decode raw Hyperlane messages to/from packed hex bytes using the CLI. Use when you need to construct a message for testing, inspect a raw message from logs or a transaction, or decode a warp transfer body.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.