「pact」の検索結果

Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.

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

Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase that has trace-mcp indexed.

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

Compact the current conversation into a portable handoff document, with an optional live clarification path for compatible Codex tasks.

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

Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones. Includes stakeholder interview frameworks and continuous reassessment. Run this BEFORE test-strategy or test-planning. Use when: "risk assessment," "risk matrix," "risk heatmap," "what could break," "critical paths," "failure modes," "where to focus testing." Not for: multi-quarter QA direction — use test-strategy. Not for: a single sprint/release test plan — use test-planning. Not for: hands-on session-based bug hunting — use exploratory-testing. Related: test-strategy, test-planning, release-readiness, qa-metrics.

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

Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients. Covers schema validation with Zod 4/AJV, auth flow testing, CRUD lifecycle tests, error and header validation, pagination, and performance assertions. Use when: "API test," "endpoint test," "REST test," "GraphQL test," "schema validation," "Postman replacement." Not for: consumer-driven contract verification (Pact, broker) — use contract-testing; browser UI flows — use playwright-automation. Related: contract-testing, test-data-management, ci-cd-integration, playwright-automation.

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

Decision framework for isolating every external dependency in a test suite: when to use in-process mocks, HTTP stubs (MSW, WireMock), record-replay, fault injection (Toxiproxy), or ephemeral real services (Testcontainers), and how to enforce that no real calls escape in CI. Use when: "mock service," "stub API," "fake service," "WireMock," "MSW," "Toxiproxy," "test isolation," "dependency management," "stub an external API in CI." Not for: consumer-driven contract verification (Pact, broker) — use contract-testing; standing up a full Docker Compose env or seed data — use test-environments; broad resilience/game-day fault campaigns — use chaos-engineering. Related: contract-testing, test-environments, api-testing, test-data-management, chaos-engineering.

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

GitHub issue creation skill. Analyzes the entire codebase impact based on user request, then creates a structured issue with AI-verified/human-judgment-needed/caution sections. /issue "issue description" Trigger: "/issue", "이슈 만들어", "issue 만들자", "깃헙 이슈"

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

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection, auto-merge candidates, labeling). Also covers creating, inspecting, and repairing a CodeScope index. Use for: code structure, who calls what, why something changed, similar functions, module boundaries, bug tracing, class relationships, PR risk/conflicts, or any question benefiting from a code knowledge graph. Applies when a `.codegraph` index exists in the workspace, or when the user wants to create one.

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

Cucumber runs behavior-driven (BDD) tests written as plain-language Gherkin feature files and matches each Given/When/Then step to code. Use when the user wants to write feature files, implement step definitions in JavaScript or TypeScript with cucumber-js, share state through a World, add hooks, tags and profiles, or run BDD scenarios in CI. Also use when the user mentions "cucumber," "BDD," "Gherkin," "feature files," "given-when-then," "step definitions," or "behavior-driven." For contract testing, see pact.

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

Work with climate data, models, and projections for climate impact assessment, downscaling, and scenario analysis using CMIP6 and other climate datasets. Use when "climate model, climate projection, CMIP6, climate data, downscaling, climate scenario, RCP, SSP, global warming, " mentioned.

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

Draft a personalized cold email to a prospect based on the SEO audit findings. Reads the audit JSON for the given domain, picks the 2-3 most impactful issues, and writes an outreach email that references specific data (current ranking, traffic value, named issues) so it doesn't look like spam.

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

Install a per-turn canary signal (e.g. starting every reply with the user's name and a turn counter) so silent context degradation becomes visible the moment it happens, and run a recovery protocol when the canary trips. Use when the user mentions a "canary", "context canary", or "canary check", asks to detect context rot / compaction / drift, says "you stopped using my name" or "did you lose context", asks "how degraded is your context", or wants an early-warning system for long agent sessions.

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

Axiom — First-Principles Assumption Auditor / 第一性原理拆解器 workflow skill. Use this skill when the user needs First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Axiom — First-Principles Assumption Auditor / 第一性原理拆解器 workflow skill. Use this skill when the user needs First-principles assumption auditor. Classifies each hidden assumption (fact / convention / belief / interest-driven), ranks by fragility × impact, and rebuilds conclusions from verified premises. Bilingual: auto-detects Chinese or English and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

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

Session 回顧報告：提取本次對話的關鍵決策、完成事項與改善建議。適合 session 結束前或 /compact 前使用。

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

60-Second Agency Snapshot — rapid 5-dimension assessment without subagents, outputs a compact scorecard

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

Trim transcript clutter to extend session lifetime — analyze, prune a copy, or toggle the after-each-turn service. Dry-run by default; gains land at resume/compaction, not the current turn.

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

Compact the current conversation into a handoff document for another agent to pick up.

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

SE Ranking AI visibility analyst (extension). Tracks AI Share-of-Voice across ChatGPT, Gemini, Perplexity, AI Overviews, and AI Mode in a single query. Highest-impact new extension per the v2 gap analysis — no other vendor covers all 5 AI platforms in one API.

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

Transform weak resume bullets into achievement-focused statements with metrics and impact

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

Identify, evaluate, and prioritize design opportunities using impact-effort frameworks and strategic criteria.

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

Communicate design's contribution to business and user outcomes in terms that resonate with stakeholders.

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

将累加型量值指标的周期波动拆解为结构变动、趋势变动和事件影响。当需要量化时间因素对指标变动的影响时调用。

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