context-hunter

Analyze codebase patterns and conventions to guide safe changes.

64|24|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/MrLesk/agents-council --skill context-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-hunter
Source: https://github.com/MrLesk/agents-council/tree/main/.codex/skills/context-hunter
Command: npx skills add https://github.com/MrLesk/agents-council --skill context-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover patterns, conventions, and unwritten rules in a codebase to guide safer, faster changes.

Core Features & Use Cases

  • Pattern discovery: Identify recurring solutions, data flows, and schema usage to reduce duplication.
  • Convention detection: Highlight naming schemes, testing patterns, and architectural norms for consistency.
  • Assumption validation: Surface potential inconsistencies before implementation and refactoring.

Quick Start

Ask the AI to scan the repository for existing patterns, naming conventions, and unwritten rules and summarize findings before starting work.

Frequently Asked Questions about context-hunter

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

FAQPage Schema
How do I discover existing codebase patterns and conventions before refactoring?

Codebase pattern discovery works by analyzing naming conventions, data flows, schema usage, and test patterns across a project. It surfaces actionable guidance on unwritten rules so you can validate assumptions and maintain consistency before implementing features or fixes.

What's the best way to analyze naming conventions and data flows in a codebase?

The best way to analyze naming conventions and data flows is to scan the repository for established patterns and testing norms. This detects architectural norms and schema usage, providing actionable guidance to reduce duplication and maintain consistency during development.

Can I validate assumptions about unwritten codebase rules before starting a bug fix?

Yes, you can validate assumptions by scanning the project for existing patterns, naming schemes, and data flows. This surfaces potential inconsistencies and unwritten rules before implementation, ensuring your bug fix aligns with established conventions.

How do I ensure consistency with established conventions when adding a new feature?

Ensure consistency by analyzing the codebase for existing naming schemes, data flows, and test patterns before implementation. This surfaces unwritten rules and architectural norms, guiding your feature development to align safely with the project's established conventions.

When do I need to scan a repository for test patterns and schema usage?

You should scan for test patterns and schema usage before refactoring or adding features. This detects established conventions and recurring solutions, surfacing actionable guidance to prevent inconsistencies and ensure new code aligns with existing data flows.