skills.rest
artk0de
artk0deCOMMUNITY
Explore all skills by this author →
GitHub

analytics-rerank

Reorder code search results using git-based structural signals.

11|3|Updated Jan 29, 2026
Search Tags:#git#analytics#hotspots#code-search#tech-debt#rerank
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill analytics-rerank
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analytics-rerank
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/tea-rags/skills/analytics-rerank
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill analytics-rerank

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standard code search often retrieves irrelevant or unstable code because it ignores the historical context of the codebase. This skill solves the problem of agents copying bug-prone, legacy, or siloed code by reordering search results based on git history and structural signals.

Core Features & Use Cases

  • Preset-based Reranking: Apply pre-configured logic for common tasks like identifying hotspots, tech debt, or security-sensitive legacy code.
  • Custom Weight Composition: Build bespoke ranking models using specific signals like bug-fix rates, ownership, and churn to suit unique project needs.
  • Use Case: When performing a security audit, use this skill to prioritize old code in authentication paths that has a high history of bug fixes, ensuring the agent focuses on the most critical areas.

Quick Start

Invoke the analytics-rerank skill to apply the hotspots preset to your current search results for identifying bug-prone areas.

Frequently Asked Questions about analytics-rerank

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve code search results to avoid retrieving bug-prone legacy code?▼

Git-aware code search reranking improves results by integrating structural signals like authorship, churn, and bug-fix frequency, ensuring agents retrieve stable, high-quality context for refactoring instead of legacy code.

What is the best way to identify technical debt and bug hotspots in a codebase?▼

Identifying technical debt is best achieved by reordering code search results using a hotspots preset, which analyzes git history to prioritize areas with high churn and frequent bug fixes.

Can I prioritize code search results for a security audit based on git history?▼

Code search results can be prioritized for security audits by applying custom weight composition to git signals, highlighting old code in sensitive paths that has a high history of bug fixes.

Does code search reranking work without external dependencies?▼

Code search reranking works without external dependencies by utilizing live registry schemas for signal weighting and preset selection to reorder results based on git history.

How do I build a custom ranking model for code search using git signals?▼

Build a bespoke ranking model for code search by composing custom weights from specific git signals like bug-fix rates, ownership, and churn to suit unique project requirements.

Related Skills

Explore More Software Engineering Skills→
bitwardenbitwarden
129

retrospecting

Generate structured retrospective reports from Claude Code session data.

Official
Intermediate
artk0deartk0de
11

brainstorming

Enrich creative code brainstorming with git-based technical debt and hotspot signals.

Community
Advanced
devrelaicomdevrelaicom
37

midnight-mcp:mcp-search

Search Midnight Compact code, TypeScript SDK, and docs with technique-aware refinement.

Official
Advanced
lis186lis186
46

history-analyzer

Analyze git history to identify hotspots, coupling, and knowledge distribution.

Community
Basic