codebase-indexer
Build a token-efficient codebase index before deep analysis or handoff. Use when you need a reusable map of symbols, files, and packed context for large repositories.
What this skill does
# Codebase Indexer
Create a compact index that separates structural discovery from full-content reads.
## Use this skill when
- a repo is too large for naive full-file reads
- you need a symbol or file inventory before planning changes
- you want a reusable handoff artifact for another model or agent
- you need token-aware codebase context instead of ad hoc search results
## Pipeline
1. **Scan structure first**
- Prefer Serena symbol tools when available.
- Otherwise use `ast-grep` plus `tree-sitter`-style structural extraction to map files, symbols, and stable anchors.
2. **Build the index**
- Record file paths, symbol names, line ranges, ownership hints, and high-value entry points.
- Keep this pass structural; do not dump full files unless the file is small or critical.
3. **Pack selected slices**
- Use the repo's `repomix` workflow to bundle only the relevant subtrees or filtered files.
- Keep the packed output scoped to the feature, subsystem, or question being studied.
4. **Shape the output**
- Convert repeated records, inventories, or symbol tables into TOON-style summaries when token budget matters.
- Keep prose short and let the structured output carry the detail.
5. **Persist only when useful**
- Default to ephemeral session output.
- For repeat work, store the index in SQLite locally or Turso remotely so later sessions can query file and symbol metadata without rebuilding everything.
## Minimal command set
```bash
# Structural scan
ast-grep --lang ts -p 'class $NAME { $$$BODY }' src/
tree-sitter tags src/**/*.ts
# Filtered pack
repomix --include "src/**,docs/**" --style markdown -o index-pack.md
# Output shaping
cat index-pack.md | toon
```
## Output contract
Return:
1. top-level file map
2. important symbols with file and range
3. packed artifact path or scope
4. compressed summary format used
5. persistence choice, if any
## Reference-only inputs
- `token-pilot` is a useful external MCP pattern for AST-aware lazy reads and token-budget reduction.
- Do not add it to tracked repo settings by default; use it as design input for the indexing workflow instead.
## Notes
- Favor symbol indexes over raw dumps.
- Rebuild only the changed slice after edits.
- Keep handoff artifacts small enough for the next model to consume directly.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.