magic-query

Searches project repositories, issue trackers, and design notes to surface relevant knowledge.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill magic-query
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: magic-query
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/magic-query
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill magic-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly surface relevant project knowledge, patterns, and past decisions to inform current work and avoid rework.

Core Features & Use Cases

  • Surface context from design notes, issues, and code comments to guide tasks.
  • Identify recurring patterns and decisions to improve consistency across tasks.
  • Use case: a developer asks for the latest decision on a design trade-off and retrieves it from the knowledge base.

Quick Start

Provide a search query to log and surface relevant project knowledge.

Frequently Asked Questions about magic-query

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

FAQPage Schema
How do I query project knowledge to find past design decisions?

Querying project knowledge involves applying a search query to project repositories, issue trackers, and design notes to surface relevant past decisions and actionable context for current tasks.

What is the best way to retrieve context from design notes and code comments?

Retrieving context from design notes and code comments requires applying search queries across project documents to identify recurring patterns and surface accessible results for chat-based workflows.

Can I surface project context from issue trackers for chat-based workflows?

Yes, you can surface project context from issue trackers by querying project knowledge bases to extract actionable information and ensure results are accessible to chat-based workflows.

How do I identify recurring patterns and gaps in project documentation?

To identify recurring patterns and gaps in project documentation, apply targeted queries to project repositories and design notes to surface actionable context and missing information.

Does querying project knowledge support replaying results for audits?

Querying project knowledge supports replaying results for audits by logging search queries and ensuring surfaced context from project documents and prior decisions remains accessible.