القائمة
Use when a contributor opens a pull request and a maintainer needs to decide whether to merge, patch-and-merge, request changes, or discard/close it.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when deploying the HushhTech web app to UAT or PROD, triggering the deploy-uat / deploy-prod GitHub Actions workflows, picking a safe "green main" SHA to ship, or when deployments feel slow and you want to cut the CI/CD cycle time. Trigger this whenever the user mentions deploying, shipping, releasing, pushing to UAT / prod / Cloud Run, a slow build or deploy pipeline, or asks how to make deploys faster — even for tiny changes. Covers the exact deploy procedure, the safety gates, the full pipeline anatomy, and a prioritized playbook of levers to reduce deploy time.
Use when deciding which checks are authoritative for a Hushhtech PR and whether the right proof exists for the changed behavior.
Use when working on Hushhtech PR checks, CI/CD, branch protection, merge queue, deploys, env parity, or operational verification.
Use when auth, env, secrets, fail-closed behavior, or sensitive API routes make a Hushhtech PR risky to patch or merge.
Use whenever a task involves Supabase for this repo — editing or deploying edge functions, changing edge-function secrets, running migrations, or auditing Supabase dashboard config. Prefer the Supabase CLI for writes when the user has explicitly asked for deployment and the target project/ref is confirmed. If CLI is blocked, fall back to the user's Chrome session on port 9223 where ankit@hushh.ai is logged in. Trigger on any mention of Supabase edge functions, secrets, migrations, or "deploy create-link-token / an edge function".
Use whenever a task involves Supabase for this repo — editing or deploying edge functions, changing edge-function secrets, running migrations, or auditing Supabase dashboard config. Prefer the Supabase CLI for writes when the user has explicitly asked for deployment and the target project/ref is confirmed. If CLI is blocked, fall back to the user's Chrome session on port 9223 where ankit@hushh.ai is logged in. Trigger on any mention of Supabase edge functions, secrets, migrations, or "deploy create-link-token / an edge function".
| name | oss-contribution-triage |
| description | Use when a contributor opens a pull request and a maintainer needs to decide whether to merge, patch-and-merge, request changes, or discard/close it. |
oss-contribution-triage-intakerepo-context, repo-operations, and direct product implementation skills.owneross-contribution-triageOwned repo surfaces:
.codex/workflows/contribution-triagedocs/reference/operations/oss-contribution-triage.mddocs/reference/operations/pr-decision-rubric.md.codex/skills/oss-contribution-triage/references/decision-buckets.mdNon-owned surfaces:
repo-operationsquality-contractssecurity-auditdocs-governancefrontendbackendCONTRIBUTING.mdSECURITY.mddocs/reference/operations/ci-governance.mddocs/reference/operations/oss-contribution-triage.mddocs/reference/operations/pr-decision-rubric.md.codex/skills/oss-contribution-triage/references/decision-buckets.mdrepo-operations whether the CI story is complete and trustworthy.quality-contracts what proof is authoritative for the changed behavior.security-audit whether maintainer patching is unsafe.Merge, Patch-and-merge, Request changes, or Discard/close.repo-operations.quality-contracts.security-audit.docs-governance.frontend, frontend-design-system, backend, or backend-api-contracts.npm run env:check
npm run lint:ci
npm test
npx tsc --noEmit
npm run build:web