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

Use for authorized macOS and Mach-O reverse engineering including codesign, Objective-C/Swift recovery, endpoint security surfaces, and Apple platform malware analysis.

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

Use for authorized source-code security review and SAST workflows including Semgrep, CodeQL patterns, dangerous API hunting, and fix verification.

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

Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.

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

Use for authorized email security review including phishing analysis, header authentication (SPF/DKIM/DMARC), BEC patterns, and mailbox token abuse research.

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

Use for software supply-chain security assessment covering SBOM, SCA, CI/CD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.

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

Use for authorized RF/SDR security research including signal identification, replay feasibility study in shielded labs, and wireless protocol analysis outside classic Wi-Fi.

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

Use for authorized Android or iOS application reverse engineering and security testing, including APK or IPA analysis, runtime instrumentation, SSL pinning, and platform protection checks.

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

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

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

Use after a phase executes, when the user wants to test the built features themselves. Runs one conversational UAT test at a time into {phase}-UAT.md and, when something fails, diagnoses it and queues fix plans for /gsd-execute-phase.

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

Use when validation or test coverage is missing on a phase that already shipped. Audits or reconstructs VALIDATION.md, fills the gaps and generates the missing test files.

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

Use for authorized security assessment of REST, GraphQL, WebSocket, or SOAP APIs, including discovery, authentication, authorization, rate-limit, and CI/CD testing.

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

Use to re-verify the threat mitigations of a phase that already shipped, or when the user asks to audit SECURITY.md. Audits an existing SECURITY.md, runs from a PLAN.md threat model, or exits if the phase never ran.

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

Use after /gsd-audit-uat when the user wants the findings fixed, not just listed. Classifies each issue as auto-fixable or manual and fixes the auto-fixable ones with test verification and atomic commits; --severity sets the floor.

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

Use when the user says run the rest autonomously, overnight, or hands-off through the remaining phases. Runs discuss, plan, execute per phase, pausing only for user decisions, then milestone audit, complete, and cleanup.

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

Use before archiving a milestone, or when the user asks whether a milestone met its definition of done. Aggregates phase VERIFICATION.md files, tech debt and deferred gaps, then runs a cross-phase integration check.

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

Use when a milestone audit reported gaps and you want the fix phases created in one pass. Reads MILESTONE-AUDIT.md, groups gaps into phases, adds them to ROADMAP.md and offers to plan each one.

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

Use when a completed phase needs unit or E2E tests, or the user asks to add tests for phase N. Classifies implementation files into TDD, E2E, or skip, gets plan approval, then generates RED-GREEN tests from SUMMARY.md and UAT criteria.

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

Use when the user asks what UAT or verification items are still outstanding across phases, or wants a prioritized manual test plan. Scans every phase for pending, skipped, blocked and human_needed items and flags stale docs.

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

Use when implementing any feature or bugfix, before writing implementation code

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

Your software-engineering brain trust. Named personas across 11 cells covering cloud architecture, reliability/SRE/observability, data and storage, security, FinOps, languages and runtimes, systems programming, web and frontend…

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

Use when implementation is done and tests pass and the user must choose to merge locally, open a PR, keep the branch, or discard it. Presents those four options, executes the choice, and cleans up the worktree for merge and discard.

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

Detailed completeness audit of all project documents. Use when someone asks "are we ready for production", "audit our docs", "readiness check", "nfr tracker", or "what's missing". Do NOT use for a quick command listing — use /pmstudio instead. Scans every document for section-level completeness, reports staleness, and gives prioritized gap-closure recommendations.

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

Use when asked to generate tests for a file, module or component, to raise coverage, or to bootstrap a suite for untested code. Detects the project's test framework and conventions first, then writes unit, integration and edge-case tests.

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

Audit token consumption across agents, skills, MCP servers, and rules. Identifies bloat, redundant components, and produces prioritized token-savings recommendations. Use when the context window is filling up too fast or before adding new components.

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