Build and review a bounded CI gate for Algolia index configuration and disposable-index smoke tests. Use when search changes need pull-request evidence without mutating production. Trigger with "Algolia CI", "test Algolia in GitHub Actions", or "search deployment gate".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
This skill adds a deterministic CI lane for code that owns Algolia records, settings, or query behavior. It separates offline contract tests from an optional network smoke test against an explicitly disposable index.
Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan.
Use a repository secret containing a custom key limited to the disposable index and required ACLs. Do not use an Admin key or expose any write key to forked pull requests.
Do not enable secrets for untrusted fork code, reuse a production index, or delete an index whose generated name was not validated. Require review for workflow-permission changes.
Return the workflow diff, secret and ACL requirements, offline results, smoke-test evidence, cleanup receipt, and the exact conditions under which the network job runs.
| Condition | Response |
|---|---|
| Secret unavailable | Skip the protected smoke job while keeping offline tests required. |
| Index name is not disposable | Fail before the first write. |
| Task does not complete | Capture task ID and request ID; preserve cleanup. |
| Cleanup fails | Fail the job and identify the retained test index. |
Use this compact input and expected handoff to calibrate scope and evidence quality.
Input:
repository=search-service; event=pull_request; smoke=protected
Expected handoff:
offline=pass; live=skipped-for-fork; production-writes=0
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Build a synthetic-data CI gate for customer-controlled Abridge integration code without calling undocumented vendor interfaces. Use when adding regression checks to an Abridge deployment repository. Trigger with "test the Abridge integration".
日本語の概要は準備中です。原文の説明を表示しています。
Triage Abridge recording, note-review, Epic handoff, and access failures from observed evidence without inventing vendor error codes. Use when an Abridge clinical workflow is degraded. Trigger with "diagnose this Abridge issue".
日本語の概要は準備中です。原文の説明を表示しています。
Design and verify the clinician workflow from consent through recording, draft review, Linked Evidence, and final note disposition. Use when implementing or auditing an Abridge clinical documentation pathway. Trigger with "map the Abridge note workflow".
日本語の概要は準備中です。原文の説明を表示しています。
Verify the approved handoff of clinician-reviewed Abridge note sections into Epic templates and downstream workflows. Use when configuring or auditing Abridge-to-Epic documentation flow. Trigger with "verify the Abridge Epic handoff".
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate Abridge adoption, workflow value, and avoidable operational friction without inventing prices or vendor billing meters. Use when reviewing an Abridge rollout or renewal. Trigger with "analyze Abridge value".
日本語の概要は準備中です。原文の説明を表示しています。
Produce a PHI-minimized Abridge support bundle with provenance, redaction, and protected escalation boundaries. Use when support needs reproducible evidence for an Abridge issue. Trigger with "build an Abridge debug bundle".
日本語の概要は準備中です。原文の説明を表示しています。