Results for “preflight-check”

Validates Bicep deployments to Azure before execution, including syntax checks, what-if analysis, and permission verification.

Runs a read-only pre-deploy verification gate covering git status, builds, tests, migrations, secrets, and commit conventions, then reports READY or NOT READY.

Scans a DICOM series folder to extract header metadata and produce a preflight verdict without decoding pixel data.

Verify work before committing, pushing, or requesting review

Use when a commit's changes are finished and about to be presented for review. Runs the checks that catch the objections the user would otherwise raise, before they spend time reviewing.

Pre-landing PR review. (gstack)

Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes.

Collects launch inputs and runs preflight checks before executing TAO workflows such as AutoML, training, evaluation, inference, export, TensorRT engine generation, or DEFT jobs on supported platforms.

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)

Track flight status, delays, and search routes. Uses FlightAware data.

The pre-share gate for a Superhuman Docs (Coda) document. Before a doc reaches a reader, run the QA checklist, choose the interaction mode, set the publish frame, and confirm the share. Catches the broken formula, the wall of text, the orphaned bullet, the missing cover, the wrong audience. Trigger on "is this doc ready to share", "publish this doc", "QA this doc", "ship-check", "final pass before I send", "which interaction mode", or any moment a Superhuman Doc is about to leave the building.

Runs a structured self-review checklist before committing substantial code changes, covering edge cases, error paths, test coverage, documentation, and code quality.

开发前 Git 前置检查 — 防多 AI 并行开发冲突。每次改代码前先 fetch + diff 检查远端是否有新提交。

Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Verifies a code change before it lands by scanning the staged diff, running tests, and delegating to an independent reviewer.

Donahoe Loop audit gate before execution. Trigger: 'audit plan', 'check plan', 'review plan', 'plan audit', 'plan check', 'before we build', 'before execution', 'validate the plan', 'is this plan solid', 'plan review'. Owns pre-execution audit intent -- fires before any foreign plan-checker.

Scans a codebase for security, database, deployment, code quality, AI/LLM, dependency, frontend, and observability issues before deployment. Intercepts deploy commands and blocks until critical items pass.

Preview server start, stop, and status check. Local development server management.

Lightweight ContentShake AI self-check the /draft stage can call before saving. Returns just SEO + Quality scores (no full optimization) so the writer knows whether the draft is in winning territory before /quality-check runs. Fails soft when SEMRUSH_API_KEY is unset.

Comprehensive verification workflow before merging changes to production.

Runs a structured three-question lazy-check on significant output before submission, forcing root-cause analysis, alternative consideration, and outcome verification.

Review a ticket or PR through focused specialist lenses: scope, architecture, security, tests, AC coverage, and PR metadata.

Gates a git branch before merge by running code review, security, test, and accessibility passes on the diff, then emits a single verdict.

旅行信息查询 - 去哪儿/携程/飞猪数据查询（Expedia 中国版）

Preview and verify imported content in a local AEM Edge Delivery Services development server, validating rendering and comparing with the original page.

Use when using Probe SDK.

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Deployment command for production releases. Pre-flight checks and deployment execution.

Review local code changes for concrete correctness, regression, security, and test gaps before shipping.

Forces investigation of file dependencies before editing code to prevent cascade failures.