adv-improve

Analyze repository state to identify evidence-backed improvement opportunities across security, reliability, and architecture.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Sharper-Flow/Advance --skill adv-improve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adv-improve
Source: https://github.com/Sharper-Flow/Advance/tree/main/skills/adv-improve
Command: npx skills add https://github.com/Sharper-Flow/Advance --skill adv-improve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the challenge of identifying technical debt, security vulnerabilities, and architectural drift in a codebase without relying on subjective opinion or manual, error-prone audits.

Core Features & Use Cases

  • Systematic Analysis: Performs structured scans across security, reliability, testing, and observability categories to surface high-impact findings.
  • Landscape Comparison: Compares local implementation against official documentation and external industry patterns to detect drift.
  • Use Case: Use this skill to generate a comprehensive research pack for a legacy module, identifying critical security gaps and outdated dependencies before starting a refactor.

Quick Start

Run the adv-improve skill to scan the current directory and generate a research pack identifying potential architectural improvements and technical debt.

Frequently Asked Questions about adv-improve

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

FAQPage Schema
How do I identify technical debt and architectural drift in a codebase?

To identify technical debt and architectural drift, analyze repository state to discover evidence-backed improvement opportunities across security, reliability, and architectural domains. This process generates structured research packs and deviation reports validated against industry standards.

How do I generate a research pack for a legacy module before refactoring?

Generate a research pack for a legacy module by running systematic structured scans across security, reliability, testing, and observability categories. This surfaces high-impact findings and compares local implementation against official documentation to detect drift.

What is evidence-backed engineering improvement discovery?

Evidence-backed engineering improvement discovery is the process of analyzing repository state to find security vulnerabilities and architectural drift without relying on subjective opinion or manual audits. It validates findings against external documentation and local conventions.

Can I scope code quality analysis to specific files or directories?

Yes, you can scope code quality analysis to specific files, directories, or symbols. This targeted approach ensures the structured scans and deviation reports focus precisely on the defined components within your repository.

How do I detect security vulnerabilities without manual error-prone audits?

Detect security vulnerabilities without manual audits by analyzing repository state to identify evidence-backed improvement opportunities. This approach systematically scans security categories and compares local implementation against official documentation to identify gaps.