「verify」の検索結果

[Codex] Use when you need to run the full Codex mirror sync + verify pipeline (migrate → hooks → context → verify) standalone, no npm/package JSON needed.

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

[Testing] Use when you need to verify integration tests pass after writing and reviewing them.

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

SOP for the micro-execution C.O.R.E. phase. Trigger when: - Implementing plan steps, managing code changes at commit boundaries, and verifying incremental progress. - Navigating states: Absorb, Clarify, Plan, Execute. - Prompt contains: /core, core workflow, absorb, clarify, execution invariants, commit boundary, verify assertion.

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

SOP for structured documentation lifecycle. Trigger when: - Designing, writing, reviewing, or auditing large-scale documentation structures. - Navigating phases: Audit, Plan, Draft, Review, Verify. - Prompt contains: /doc, doc workflow, audit, draft, review, verify, documentation debt.

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

Cloudflare Turnstileをprojectへend-to-endで導入する。codebaseを調査し、Cloudflare APIでwidgetを作成し、適切なformへ埋め込み、既存backendへ正式なserver-side siteverifyを接続して検証する。Turnstile追加、CAPTCHA設定、botからのform保護、Turnstile連携修正を依頼されたときに使用する。developers.cloudflare.com/turnstile/spinの中核手順へAIDD固有の安全規則を重ねたSkill。

Run Tamanu pre-release verification checks: verify that hotfixes on the current release branch are merged forward to main, and that hotfixes from prior release branches are included in the current release. Use when the user wants to run "pre-release checks", verify hotfix integrity before cutting or shipping a Tamanu release, confirm a release/X.YY branch is safe to release, or check that no hotfix has been orphaned (left on neither main nor the current release). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for deciding which tests to run (see scope-tamanu-release-tests).

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

Run the Tamanu release-branch CUTOFF checks when preparing to cut a new release/X.YY branch: confirm the previous release's hotfixes are merged to main, reconcile the commits since the previous release against the "Merged to main" card list from Linear, and scan for data/reporting/schema changes. Use when the user is cutting a Tamanu release and wants to verify the codebase is ready, wants to check main against the previous release branch, or wants to reconcile commits with a Linear "Merged to main" column (they should paste the card list). Handles Tamanu's train-release model (release/X.YY branches vs vX.YY.Z patch tags) and the cherry-pick model where the same logical fix has different SHAs on different branches. Purely git-based — no live database or Canopy access needed. Not for verifying an existing release branch's hotfix integrity (see pre-release-checks) or for deciding which tests to run (see scope-tamanu-release-tests).

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

本番と同じ失敗を本番前に検出するためのテスト階層設計スキル。 DB方言差、実依存関係、永続化確認、timezone差、packaging整合性、 adversarial regressionをunit/integration/e2e/smoke/packagingに 適切に割り振り、PR CIで最低限の本番同等性を保証する。 Use when designing production-parity tests, closing test blind spots, building smoke suites for real dependencies, verifying persistence beyond UI success, or creating adversarial regression backlogs.

既存コード・既存関数・既存モジュールの暗黙契約を抽出するスキル。 戻り値型、副作用、例外、前提条件、境界条件、環境依存挙動を確認し、 reuse前のリスクを可視化する。名前やコメントではなく実際の挙動から 契約を読み取り、不一致を分類し、再利用可否を判定する。 Use when reusing legacy code, verifying actual behavior of existing functions, or extracting implicit contracts before implementation. Covers: hidden contract, implicit contract, reuse risk, legacy behavior, 暗黙契約, 既存資産調査. Analyzes return types, side effects, exceptions, preconditions, boundary conditions, and environment-dependent behavior.

Verify Rash Studio scenes, ActionScript subset behavior, resource links, portable embeds, exports, and desktop or mobile interaction. Use for Rash acceptance checks, compatibility review, security review, or release validation.

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

Verify someone else's code fix against your own live corpora (agent transcripts, sessions, memory files) before trusting or merging it. Use when an external PR or patch touches how transcripts, sessions or agent memory are read. Triggers: /corpus-bench, run it on our corpus, verify the fix on our transcripts, corpus bench.

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

Verify SIPS proof surfaces before reporting completion. Use when asked to scan, verify, validate, prove, audit, or check whether a repo or SIPS install is coherent.

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

Remove signs of AI-generated code from a codebase while preserving behavior. Use when editing or reviewing code to make it read like a human engineer on this team wrote it. Works through a test-guarded detect-modify-verify loop: pin down the functional contract and edge cases first, write or run tests as a safety net, then rewrite AI tells (redundant comments, emoji, verbose names, reflexive try/except, defensive null-guards, over-decomposition, speculative abstraction, dead code, non-idiomatic constructs, hallucinated dependencies) and re-verify after every change. The tests decide whether a defensive block is slop or a real safeguard.

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

TDD を主張する実装の RED/GREEN/REFACTOR VERIFY 証跡（tdd-ledger）の妥当性を検査し、フェーズ順序・exitCode・test-cases との対応の欠落や偽装を検知する

Verify an open factory PR before human review - re-runs gates, checks the test proves the fix, checks scope and test tampering. Use when reviewing a factory PR, running the PR review routine, or asked to independently check a change.

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

Independently verify a factory pull request, including fail-closed gates, negative test proof, scope, and load-bearing review.

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

Validates code fixes by running the code, checking compilation, verifying runtime behavior, and confirming fixes resolve the reported issue. Use when verifying that bug fixes actually work at runtime.

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

Collect, download, and verify App Store Connect Analytics reports with asc. Use when users need to discover analytics report requests, select report instances by processing date or granularity, download every segment, or verify downloaded files against Apple's size and MD5 metadata before analysis.

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

Use this skill when writing end-to-end tests, browser automation, or verifying user flows in a real browser. Trigger words: E2E, Playwright, ブラウザテスト, ユーザーフロー, 結合テスト, シナリオテスト, ログインテスト, getByRole, expect.

Plan, verify, and track demo/marketing video production in Busabase — idea to hook/pain-point/storyboard, codebase claim verification, recording progress, post-production handoff, and HyperFrame (Remotion) linkage. Use when the user invokes $kelly-demo-video-factory or /kelly-demo-video-factory, wants to plan a product demo video, write a storyboard, verify a video script's product claims against the codebase, track which shots are recorded, or hand a finished storyboard off to editing/Remotion.

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

Design and verify audio finishing for Japanese or English short-form social video. Use for 短尺SNS, BGM/効果音, テンポ調整, 意味ベース配置, dialogue-first mixing, or existing rough cut audio finishing with pinned local assets and internal-review QA.

After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change.

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

Verify that a Markdown file has correct formatting — headings, lists, links, code blocks, spacing, and consistent style.

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

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

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