agentsclimarketplace

Context hunter

Skill foryourhealth111-pixel/Vibe-Skills/bundled/skills/context-hunter

VibeSkills is a general-purpose Skill that automatically routes local Skills and intelligently orchestrates harness workflows.

Install
npx -y skills add foryourhealth111-pixel/Vibe-Skills --skill context-hunter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.0 KB, as published. Nobody here has run it

Context Hunter

Before writing code, investigate how similar problems are already solved in this codebase.

Before Implementation

Discover Existing Patterns

  1. Find analogous features: Search for code that solves similar problems. Study it before proposing your approach.
  2. Trace data flow: How does similar data move through the system? Note caching, validation, and error handling patterns.
  3. 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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.