Agent Skills
› foryourhealth111-pixel/Vibe-Skills
› context-hunter
context-hunter
GitHub在编码前分析代码库模式、约定和隐性规则，确保变更与现有风格一致。通过查找类似功能、数据流和工具函数，识别命名及测试惯例，验证假设并规避冲突，实现无缝集成。
Trigger Scenarios
实现新功能
修复Bug
重构代码
Install
npx skills add foryourhealth111-pixel/Vibe-Skills --skill context-hunter -g -y
SKILL.md
Frontmatter
{
"name": "context-hunter",
"description": "Discover codebase patterns, conventions, and unwritten rules before making changes. Use when implementing features, fixing bugs, or refactoring code."
}
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
Version History
- f627ab5 Current 2026-07-25 04:40
