meaning-query

Query the .meaning/ index with natural language to locate files by intent and tags.

1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/bozaah/meaning-fs --skill meaning-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meaning-query
Source: https://github.com/bozaah/meaning-fs/tree/main/.claude/skills/meaning-query
Command: npx skills add https://github.com/bozaah/meaning-fs --skill meaning-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides instant, natural-language semantic search over the .meaning/ index, enabling you to surface files by intent, tags, and relationships without grep-based workflows.

Core Features & Use Cases

  • Natural language queries over the meaning index to locate files by tags, relationships, concepts, and intents.
  • Use cases include finding where a function is implemented, identifying files that need review, and discovering related artifacts across a codebase.
  • Quickly answer questions like "Where is parsing implemented?" or "Show me all configuration files" using a deterministic, local inference pipeline.

Quick Start

Use natural language questions to query the meaning index. For example:

  • User asks: "Where is parsing implemented?"
  • Claude runs: python -m meaning query "where is parsing implemented?"

Frequently Asked Questions about meaning-query

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search a codebase to find where a function is implemented?

To find where a function is implemented, perform a natural language semantic search against the .meaning/ index using queries like "Where is parsing implemented?" to surface relevant files by intent and relationships.

What is semantic search over a meaning index?

Semantic search over a meaning index is querying a local .meaning/ index with natural language to reveal file intent, tags, and relationships, replacing traditional grep-based workflows with deterministic, local inference results.

Do I need external services to run natural language queries on my codebase?

No external services are required to run natural language queries on your codebase. The skill executes via a local inference pipeline using the meaning query engine, providing fast and deterministic results entirely offline.

Can I find configuration files across a project without using grep?

You can find configuration files across a project without grep by asking the meaning index natural language questions like "Show me all configuration files" to quickly surface related artifacts and tags.

What's the best way to discover related artifacts and file relationships in a codebase?

The best way to discover related artifacts and file relationships in a codebase is to apply natural language semantic search against the .meaning/ index to reveal connections and locate files by concepts and intents.