Search results in GrepAI can be sorted to show the most important code first. You can use boosting to give higher scores to files in key folders. You can also penalize less useful code like tests and vendor files.
Boosting works by applying a factor to each file's search score. A factor greater than 1.0 increases the score. A factor less than 1.0 reduces it. For example, you can boost /src/ files by 10% and cut /tests/ files by 50%.
This skill shows you how to set up these rules in a YAML config file. Developers get more relevant results faster. Production code appears before test code in search lists.
Global
mkdir -p ~/.claude/skills/grepai-search-boostingProject
mkdir -p .claude/skills/grepai-search-boostingSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective