القائمة
Force full re-index zero downtime. Builds new versioned collection in background while search continues on current. Alias switches atomically when done. Requires explicit user confirmation — NEVER invoke automatically.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Decide HOW to write new code by inspecting git signals on neighbors — pulls strategy and templates from proven, low-churn nearby implementations rather than guessing from training data. Triggers on "implement function X", "add method to class Y", "write a helper for Z", "напиши функцию", "добавь метод". NOT for discovery or exploration — use tea-rags:explore for that. This skill activates ONCE the agent is about to write code.
Agentic-only enrichment skill — surface battle-tested reference code from project as templates for generation / modification. Three-level locality cascade (target subdomain → domain → project), quality gate by overlay labels + project-wide proven rerank preset. Returns ranked list of reference chunks + locality annotation (L1 / L2 / L3 / none). Invoked by `tea-rags:data-driven-generation` Step 2 (TEMPLATE), `dinopowers:writing-plans` (per code-gen Task), `dinopowers:executing-plans` (per Task during execute). Skipped when no `positiveIds` / `positiveCode` and no `behaviorQuery` available.
Run automated TeaRAGs install wizard from scratch — detects environment, installs deps (Node.js, tea-rags, Ollama/ONNX, Qdrant), tunes performance, configures MCP server. Progress saves to ~/.tea-rags/setup-progress.json for resumable install. Triggers on "install tea-rags", "set up TeaRAGs MCP", "configure tea-rags from scratch", "поставить tea-rags в проект". NOT for tuning an existing install — use tune for that.
Agent-only. Raise test coverage above a failed pre-commit threshold: locate the
Brainstorm code change seeing risk, ownership, tech-debt signals from tea-rags first — creative exploration grounded in actual state of affected area. Triggers on "brainstorm X", "design feature", "refactor Y", "let's discuss", "давай обсудим", "как перестроить", "что может сломаться". NOT for trivial edits or stylistic questions with no code area to enrich. Wraps superpowers:brainstorming with tea-rags risk-signal enrichment step.
Execute written implementation plan whose Tasks edit code, per-Task SAFE/CAUTION/UNSAFE git-signal verdict before edit AND code-style cascade for code-generation Tasks (style from silo authors, strategy+template from proven neighbors). Triggers on "execute the plan", "start Task N", "выполни план", "начни задачу", "run the plan", "implement the plan steps". NOT for one-off edits without a written plan. Wraps superpowers:executing-plans with tea-rags git-signal verdicts and tea-rags:data-driven-generation cascade.
| name | force-reindex |
| description | Force full re-index zero downtime. Builds new versioned collection in background while search continues on current. Alias switches atomically when done. Requires explicit user confirmation — NEVER invoke automatically. |
| argument-hint | [path to codebase] |
Runs forceReindex in background subagent. Search stays available throughout
via collection aliases.
This skill MUST ONLY be invoked when the user explicitly requests it. Agents MUST NOT auto-trigger force-reindex on stale markers, index status, or any automated signal.
Before executing, MUST:
AskUserQuestion:
question: "Force reindex will rebuild the entire index for <path>. This can take several minutes. Proceed?"
options:
- { label: "Yes, reindex", description: "Start full reindex in background" }
- { label: "Cancel", description: "Do not reindex" }
Confirm with user (see above). If user cancels, stop.
Extract path from user message or argument. If absent, use current working
directory.
Dispatch background subagent with run_in_background: true (full reindex
takes minutes — background justified):
Agent tool:
description: "Force reindex in background"
run_in_background: true
prompt: |
Call mcp__tea-rags__index_codebase with:
- path: <extracted path>
- forceReindex: true
Report the COMPLETE response as-is — every field returned by the tool.
Do not cherry-pick fields. Whatever the endpoint returns, summarize it all.
ALWAYS include the duration field — users need to see how long indexing took.
Tell the user: "Force reindex started in background. Search continues on the current index — zero downtime. You'll be notified when the new index is ready."
When background agent completes, report full result to user. Include all metrics and duration — do not summarize or omit fields.
index_codebase with forceReindex: true in the foreground/tea-rags:index instead