mvt-consult

Answer questions about existing project logic and verify implementation details against source code.

19|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-consult
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mvt-consult
Source: https://github.com/uoyoCsharp/My-Virtual-TechTeam/tree/main/.claude/skills/mvt-consult
Command: npx skills add https://github.com/uoyoCsharp/My-Virtual-TechTeam --skill mvt-consult

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you answer questions about how a project currently works without making changes or creating documentation artifacts. It is designed for moments when you need a reliable explanation of existing logic, a confirmation of implementation details, or a quick verification grounded in the actual codebase.

Core Features & Use Cases

  • Codebase Q&A: Explains project behavior, flows, and logic using existing project knowledge and source code when needed.
  • Implementation Verification: Confirms concrete facts such as whether a function retries, whether a config value is still used, or whether a behavior still exists.
  • Safe Read-Only Consultation: Stays strictly conversational, avoids editing code, avoids writing artifacts, and flags discrepancies when project knowledge is outdated compared with source.
  • Use Case: When a teammate asks whether a handler still performs a fallback path after an API failure, this Skill can inspect the relevant files and answer with a grounded citation instead of guessing.

Quick Start

Ask mvt-consult to explain how a specific feature works or to verify whether a named function, file, or behavior currently exists in the codebase.

Frequently Asked Questions about mvt-consult

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

FAQPage Schema
How do I verify if a specific function or behavior still exists in my codebase?

To verify implementation details in your codebase, you can request a read-only source analysis that confirms whether a named function, file, or fallback path currently exists using grounded citations from the actual code.

Can I check codebase logic without risking accidental code edits?

Yes, you can perform safe read-only consultation to check codebase logic without risking edits. The analysis stays strictly conversational, avoiding any code modifications, artifact creation, or file changes while explaining project flows.

What is the best way to explain how a specific feature flow works in an ongoing project?

The best way to explain a specific feature flow is through codebase Q&A that cross-references existing project knowledge with actual source code to provide reliable explanations of current behavior and logic.

Why does my project documentation disagree with what the source code actually does?

Project documentation and source code discrepancies occur when code changes outpace docs. A read-only consultation can flag these outdated documentation gaps by validating implementation details directly against the current source.

Do I need to provide source files to get answers about my project's configuration checks?

Yes, configuration checks require loaded project knowledge and source code access to perform symbol-level verification, confirm whether a config value is still used, and deliver confidence-based answers about your implementation.

Does codebase consultation support behavior confirmation for API failure handling paths?

Codebase consultation supports behavior confirmation for API failure handling by inspecting relevant files to verify whether a handler still performs a fallback path, providing a grounded answer instead of guessing.