research-improve

Propose and validate code improvements for security, quality, and maintainability.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/skylarsabo/code-ops --skill research-improve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-improve
Source: https://github.com/skylarsabo/code-ops/tree/main/plugins/researcher/skills/research-improve
Command: npx skills add https://github.com/skylarsabo/code-ops --skill research-improve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides grounded, external-best-practice improvements for existing code without writing code, streamlining the process and ensuring that proposed changes are beneficial and well-justified.

Core Features & Use Cases

  • Code Improvements Proposal: Propose improvements for code quality, security, maintainability, etc., based on both the codebase and external knowledge sources.
  • Local-First Research: Focus on understanding the existing codebase thoroughly before reaching out to external resources.
  • Verification and Disconfirmation: Rigorously verify each improvement proposal, ensuring it applies within the project's constraints and doesn't introduce new issues.

Quick Start

Use the /researcher:research-improve command to begin proposing improvements for a specific target in your codebase.

Frequently Asked Questions about research-improve

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

FAQPage Schema
How do I propose code improvements based on external best practices?

To propose code improvements, you can analyze a codebase locally and cross-reference it with external knowledge sources to suggest changes for security, quality, and maintainability without directly writing code.

What is external research for codebase analysis?

External research for codebase analysis is the process of thoroughly understanding existing local code first, then querying external knowledge to propose and verify feasible, beneficial improvements within project constraints.

How do I verify that proposed code changes fit my project constraints?

You verify proposed code changes by rigorously checking each improvement proposal against the project's specific environment and constraints, ensuring the updates do not introduce new security or quality issues.

Does this code analysis approach write code changes directly into the project?

No, this code analysis approach does not write code directly. It focuses on proposing and validating improvements grounded in the codebase and external knowledge to streamline the review process.

Can I use this for security review and maintainability analysis?

Yes, you can use this for security review and maintainability analysis. It focuses on proposing improvements for code quality and security based on both local codebase context and external sources.