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周前更新