Grepai Search Boosting

yoanbernabeu/grepai-skills/skills/search/grepai-search-boosting

作者 yoanbernabeu382d40261c0d41109c6e11872574ba0be9b064d0無授權條款收錄於 2026年10月9日更新於 2026年10月9日

Configure search result boosting in GrepAI. Use this skill to prioritize certain paths and penalize others.

僅含說明Software Development
AI 產生的概覽

設定 GrepAI 搜尋分數加權，提升原始碼路徑優先順序並降低測試、文件與第三方程式碼的排名。

功能
此技能說明如何在 GrepAI 中設定分數加權，讓搜尋結果依檔案路徑重新排序。內容介紹包含懲罰項（係數低於 1.0）與獎勵項（係數高於 1.0）的 YAML 加權設定、模式如何比對完整檔案路徑，以及係數如何影響排名。它也提供適用於標準、前端、Go、Python 與 monorepo 專案的現成設定，並附上測試與疑難排解建議。
適用情境
當搜尋結果被測試、文件、產生程式碼或第三方相依套件佔據，而你希望正式環境的原始碼排名更高時使用。也適合需要針對特定專案結構（例如前端、Go、Python 或 monorepo 程式庫）自訂結果排名的情況。
執行需求
需要 GrepAI 以及設定檔（例如 .grepai/config.yaml）。僅為說明文件，不含指令碼。

GrepAI Search Boosting

This skill covers configuring score boosting to prioritize relevant code paths and deprioritize tests, docs, and vendor code.

When to Use This Skill

  • Prioritizing source code over tests
  • Penalizing vendor/third-party code
  • Boosting important directories
  • Customizing result ranking

What is Boosting?

Boosting modifies search scores based on file paths:

Original score: 0.85 (src/auth.go)Bonus (+10%):   0.935
Original score: 0.85 (tests/auth_test.go)Penalty (-50%): 0.425

This ensures production code ranks higher than tests with similar content.

Configuration

Basic Configuration

yaml
# .grepai/config.yamlsearch:  boost:    enabled: true    penalties:      - pattern: /tests/        factor: 0.5    bonuses:      - pattern: /src/        factor: 1.1

Full Configuration

yaml
search:  boost:    enabled: true
    # Reduce scores (factor < 1.0)    penalties:      # Test files      - pattern: /tests/        factor: 0.5      - pattern: /__tests__/        factor: 0.5      - pattern: _test.        factor: 0.5      - pattern: .spec.        factor: 0.5      - pattern: .test.        factor: 0.5
      # Documentation      - pattern: /docs/        factor: 0.6      - pattern: /documentation/        factor: 0.6
      # Vendor/third-party      - pattern: /vendor/        factor: 0.3      - pattern: /node_modules/        factor: 0.3      - pattern: /third_party/        factor: 0.3
      # Generated code      - pattern: /generated/        factor: 0.4      - pattern: .gen.        factor: 0.4      - pattern: .pb.go        factor: 0.4
      # Examples and samples      - pattern: /examples/        factor: 0.7      - pattern: /samples/        factor: 0.7
    # Increase scores (factor > 1.0)    bonuses:      # Core source code      - pattern: /src/        factor: 1.1      - pattern: /lib/        factor: 1.1      - pattern: /app/        factor: 1.1      - pattern: /core/        factor: 1.2      - pattern: /internal/        factor: 1.1
      # Important directories      - pattern: /services/        factor: 1.1      - pattern: /handlers/        factor: 1.1      - pattern: /controllers/        factor: 1.1

How Factors Work

FactorEffectUse Case
0.370% reductionStrong penalty (vendor)
0.550% reductionModerate penalty (tests)
0.730% reductionMild penalty (examples)
1.0No changeNeutral
1.110% increaseMild boost (src)
1.220% increaseModerate boost (core)
1.550% increaseStrong boost

Pattern Matching

Patterns match against the full file path:

/project/src/auth/middleware.go         ^^^^         Matches "/src/" pattern

Pattern Types

PatternMatchesDoesn't Match
/tests/src/tests/auth.gotests.go
_test.auth_test.gotest_auth.go
.spec.auth.spec.tsspec/auth.ts
/src/project/src/main.goresource/file.go

Effect on Rankings

Without Boosting

Score: 0.85 | tests/auth_test.go:10-30Score: 0.82 | src/auth/middleware.go:15-45Score: 0.80 | src/auth/jwt.go:23-55

With Boosting

yaml
penalties:  - pattern: /tests/    factor: 0.5bonuses:  - pattern: /src/    factor: 1.1
Score: 0.90 | src/auth/middleware.go:15-45  (0.82 × 1.1)Score: 0.88 | src/auth/jwt.go:23-55        (0.80 × 1.1)Score: 0.43 | tests/auth_test.go:10-30     (0.85 × 0.5)

Common Configurations

Standard (Recommended)

yaml
search:  boost:    enabled: true    penalties:      - pattern: /tests/        factor: 0.5      - pattern: _test.        factor: 0.5      - pattern: .spec.        factor: 0.5      - pattern: /vendor/        factor: 0.3      - pattern: /docs/        factor: 0.6    bonuses:      - pattern: /src/        factor: 1.1      - pattern: /lib/        factor: 1.1

Frontend Project

yaml
search:  boost:    enabled: true    penalties:      - pattern: /__tests__/        factor: 0.5      - pattern: .test.        factor: 0.5      - pattern: .spec.        factor: 0.5      - pattern: /node_modules/        factor: 0.3      - pattern: .stories.        factor: 0.6      - pattern: /storybook/        factor: 0.6    bonuses:      - pattern: /src/        factor: 1.1      - pattern: /components/        factor: 1.1      - pattern: /hooks/        factor: 1.1

Go Project

yaml
search:  boost:    enabled: true    penalties:      - pattern: _test.go        factor: 0.5      - pattern: _mock.go        factor: 0.5      - pattern: /testdata/        factor: 0.5      - pattern: /vendor/        factor: 0.3      - pattern: .pb.go        factor: 0.4    bonuses:      - pattern: /internal/        factor: 1.1      - pattern: /cmd/        factor: 1.1      - pattern: /pkg/        factor: 1.1

Python Project

yaml
search:  boost:    enabled: true    penalties:      - pattern: /tests/        factor: 0.5      - pattern: test_        factor: 0.5      - pattern: _test.py        factor: 0.5      - pattern: /conftest        factor: 0.5      - pattern: /fixtures/        factor: 0.6    bonuses:      - pattern: /src/        factor: 1.1      - pattern: /app/        factor: 1.1      - pattern: /core/        factor: 1.2

Monorepo

yaml
search:  boost:    enabled: true    penalties:      - pattern: /tests/        factor: 0.5      - pattern: _test.        factor: 0.5      - pattern: /packages/deprecated/        factor: 0.3      - pattern: /packages/legacy/        factor: 0.4    bonuses:      - pattern: /packages/core/        factor: 1.2      - pattern: /packages/api/        factor: 1.1      - pattern: /packages/shared/        factor: 1.1

Disabling Boosting

To disable boosting entirely:

yaml
search:  boost:    enabled: false

Or remove the boost section from config.

Boosting vs Ignoring

ApproachEffectUse Case
IgnoreCompletely excludedDependencies, build output
PenaltyStill searchable, lower rankTests, docs, examples
NeutralDefault rankingRegular source code
BonusHigher rankCore business logic

When to Ignore vs Penalize

  • Ignore: Files you NEVER want to search (node_modules, .git)
  • Penalize: Files you RARELY want but might need (tests, docs)

Testing Your Configuration

After configuring boosting:

bash
# Search and observe rankingsgrepai search "authentication"
# Check if tests are properly deprioritizedgrepai search "test authentication"  # Should still find tests, but ranked lower

Best Practices

  1. Start with penalties: Deprioritize tests/vendor first
  2. Add bonuses sparingly: Only for truly important paths
  3. Test with real queries: Verify results make sense
  4. Don't over-penalize: 0.5 is usually enough for tests
  5. Document your choices: Add comments in config

Common Issues

❌ Problem: Tests always show up first ✅ Solution: Add penalty patterns for your test naming convention

❌ Problem: Can't find code in penalized paths ✅ Solution: Penalties reduce rank, don't hide. Use ignore for complete exclusion.

❌ Problem: Scores above 1.0 seem wrong ✅ Solution: Bonuses can push scores above 1.0; this is normal

❌ Problem: Pattern not matching ✅ Solution: Check that pattern appears in full path (use /tests/ not just tests)

Output Format

Boosting configuration status:

✅ Search Boosting Configured
   Status: Enabled
   Penalties (5):   - /tests/      → 0.5 (50% reduction)   - _test.       → 0.5   - .spec.       → 0.5   - /vendor/     → 0.3 (70% reduction)   - /docs/       → 0.6
   Bonuses (3):   - /src/        → 1.1 (10% boost)   - /lib/        → 1.1   - /core/       → 1.2 (20% boost)
   Effect: Source code ranks higher than tests with similar content

來源與署名

來源：yoanbernabeu/grepai-skills位於skills/search/grepai-search-boosting提交382d402

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 yoanbernabeu/grepai-skills 的技能

Grepai Trace Graph

yoanbernabeu

指導使用 grepai trace graph 指令建立遞迴呼叫圖，用於程式碼相依性與影響分析。

Software Development2026年10月9日

Grepai Trace Callers

yoanbernabeu

指導使用 grepai trace callers 指令找出呼叫某個函式的程式碼位置。

Software Development2026年10月9日

Grepai Trace Callees

yoanbernabeu

指導使用 grepai trace callees 指令列出某個函式所呼叫的所有函式。

Software Development2026年10月9日

Grepai Storage Postgres

yoanbernabeu

設定 PostgreSQL 搭配 pgvector 作為 GrepAI 的儲存後端，涵蓋安裝、調校與疑難排解。

DevOps & Cloud2026年10月9日

Grepai Storage Gob

yoanbernabeu

說明如何設定 GrepAI 的 GOB 本機檔案儲存後端，涵蓋設定、操作、限制與移轉。

Software Development2026年10月9日

Grepai Search Tips

yoanbernabeu

指導如何撰寫有效的 GrepAI 語意搜尋查詢，依意圖而非精確名稱尋找程式碼。

Software Development2026年10月9日

更多Software Development技能

Playground

anthropics

精選

建立自成一體的互動式 HTML 遊樂場，包含控制項、即時預覽與可複製的提示詞輸出。

Software Development37K今天更新

M5 Onboard

anthropics

精選

透過 USB 偵測 M5Stack ESP32 開發板，燒錄 UIFlow 2.0 韌體並安裝 MicroPython 應用程式套件。

Software Development37K今天更新

Cardputer Buddy

anthropics

精選

指導迭代 Cardputer-Adv 的 MicroPython 應用程式套件：新增應用程式、透過 USB 序列埠推送檔案、查看日誌並執行 REPL 指令。

Software Development37K今天更新

Web Design Guidelines

vercel-labs

精選

依據從遠端來源取得的 Web Interface Guidelines 審查 UI 程式碼，並以 file:line 形式回報問題。

Software Development32K5 週前更新

Vercel React Native Skills

vercel-labs

精選

React Native 與 Expo 最佳實務規則，涵蓋清單效能、動畫、導覽、UI 模式、狀態與 monorepo 設定。

Software Development32K5 週前更新

Vercel React Best Practices

vercel-labs

精選

Vercel 的 React 與 Next.js 效能指南，以 70 條規則的形式用於撰寫、審查與重構程式碼。

Software Development32K5 週前更新