Context Hunter
Discover codebase patterns, conventions, and unwritten rules before making changes. Use when implementing features, fixing bugs, or refactoring code.
Install
$ agentstack add skill-foryourhealth111-pixel-vibe-skills-context-hunter ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-foryourhealth111-pixel-vibe-skills-context-hunter) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: foryourhealth111-pixel
- Source: foryourhealth111-pixel/Vibe-Skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.