Context Hunter
Developmentcontext-hunterContext Hunter is an Agent Skill for development published in the foryourhealth111-pixel/Vibe-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Discover codebase patterns, conventions, and unwritten rules before making changes. Use when implementing features, fixing bugs, or refactoring code.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/foryourhealth111-pixel/Vibe-Skills/blob/HEAD/bundled/skills/context-hunter/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/context-hunter, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Context Hunter
Before writing code, investigate how similar problems are already solved in this codebase.
Before Implementation
Discover Existing Patterns
- Find analogous features: Search for code that solves similar problems. Study it before proposing your approach.
- Trace data flow: How does similar data move through the system? Note caching, validation, and error handling patterns.
- Identify utilities: Search for existing helpers before creating new ones.
Detect Unwritten Conventions
Look for implicit rules encoded in the codebase:
- Schema patterns:
deleted_atcolumns indicate soft-deletion. Audit columns indicate tracking requirements. - Naming patterns: Note consistency in
user_idvsuserIdvsuserID. - Test patterns: What's tested thoroughly reveals team priorities.
Verify Assumptions
- Run the test suite to understand current state
- Check linter and formatter configs
- Read recent commits in affected areas
- Examine database schemas for constraints
During Implementation
Match Existing Code
Your changes should be indistinguishable from existing code:
- Use the same patterns, abstractions, and utilities
- Follow the same error handling approach
- Respect module boundaries
- Match naming conventions exactly
Surface Concerns
When you discover conflicts between requirements and existing patterns:
- Ask clarifying questions before proceeding
- Flag risks you've identified
- Offer alternatives that align with codebase conventions
Checklist
Before proposing changes, confirm:
- Studied analogous features in the codebase
- Checked for reusable utilities
- Reviewed test patterns for similar functionality
- Noted naming and schema conventions
- Verified approach matches existing patterns