Context Hunter Agent Skill

Discover codebase patterns, conventions, and unwritten rules before making changes. Use when implementing features, fixing bugs, or refactoring code.

503 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

2583

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/foryourhealth111-pixel/Vibe-Skills --skill context-hunter

The instruction itself

9 sections, as written by the author

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_at columns indicate soft-deletion. Audit columns indicate tracking requirements.
Naming patterns: Note consistency in user_id vs userId vs userID.
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

Other skills for the same job

different authors, same section of the catalogue

Git Commit

by github

vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

Verification & Quality Assurance

by Microck

×2

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.

1k tokens

Codebase Cleanup Refactor Clean

by ComeOnOliver

×2

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

9k tokens

Codebase Cleanup Tech Debt

by ComeOnOliver

×2

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

6k tokens

How to use it

Copy the folder

Take foryourhealth111-pixel/context-hunter from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.