一键导入
repo-context
Use when a request starts with scanning Hushhtech, mapping repo surfaces, or choosing which owner skill should take the next step.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when a request starts with scanning Hushhtech, mapping repo surfaces, or choosing which owner skill should take the next step.
用 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 | repo-context |
| description | Use when a request starts with scanning Hushhtech, mapping repo surfaces, or choosing which owner skill should take the next step. |
repo-context-intakeoss-contribution-triage, repo-operations, and docs-governance.ownerrepo-contextOwned repo surfaces:
.codex/skills/README.mddocs/project_context_map.mddocs/reference/operations/skill-taxonomy.mdNon-owned surfaces:
oss-contribution-triagerepo-operationssecurity-auditdocs-governancefrontendbackendoss-contribution-triage..codex/skills/README.mddocs/project_context_map.mddocs/reference/operations/skill-taxonomy.mdoss-contribution-triage as soon as the request becomes a maintainer decision problem.oss-contribution-triage.repo-operations.security-audit.docs-governance.frontend or backend.rg --files .github/workflows scripts/ci src api tests docs
node -e 'const p=require("./package.json"); console.log(JSON.stringify(p.scripts,null,2))'