source-driven-development

Detects framework versions and compares code against official documentation.

11|3|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill source-driven-development-threat-vector-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-driven-development
Source: https://github.com/Threat-Vector-Security/guardian-agent/tree/main/skills/source-driven-development
Command: npx skills add https://github.com/Threat-Vector-Security/guardian-agent --skill source-driven-development-threat-vector-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ground decisions in authoritative sources to avoid relying on memory when implementing or reviewing framework-specific code.

Core Features & Use Cases

  • Locate the relevant official documentation for a detected framework and version from repository metadata.
  • Compare implemented code against sources, surface discrepancies, and provide citations.
  • Guide remediation to align code with documentation and maintain versioned guidance.

Quick Start

Identify the framework and version from the repo, fetch official sources, and surface any code-to-doc discrepancies for remediation.

Frequently Asked Questions about source-driven-development

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

FAQPage Schema
How do I verify framework-specific code against official documentation?

To verify framework-specific code against official documentation, you identify the framework and version from repository metadata, fetch authoritative sources, and surface discrepancies with citations for remediation.

How do I check if my code aligns with versioned guidance during a code review?

Checking code alignment with versioned guidance involves detecting dependencies from the repository, fetching current official docs, and surfacing conflicts where the implemented code diverges from the documentation.

What is the best way to avoid relying on memory for API migration decisions?

The best way to avoid relying on memory for API migration is to ground decisions in authoritative sources, fetching versioned guidance to compare implemented code against current official documentation.

Can I use documentation verification for boilerplate generation across multiple languages?

Yes, documentation verification applies to boilerplate generation across multiple languages by detecting the framework from repository metadata and ensuring generated code matches official docs.

Why does my code review fail to catch framework API discrepancies?

Code reviews fail to catch framework API discrepancies when they rely on memory instead of fetching official docs to compare implemented code against versioned guidance and surface conflicts.

Does official docs verification work without specifying a framework version?

No, official docs verification requires identifying the framework and version from repository metadata to fetch the correct versioned guidance and accurately surface code-to-doc discrepancies.