spotlight

Identify five concrete improvements for C# files in Retrograde.Library.

12|1|Updated Jan 16, 2024
One-click install
npx skills add https://github.com/kaosnyrb/FrankyCLI --skill spotlight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spotlight
Source: https://github.com/kaosnyrb/FrankyCLI/tree/main/.claude/skills/spotlight
Command: npx skills add https://github.com/kaosnyrb/FrankyCLI --skill spotlight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and propose concrete improvements for underviewed code in Retrograde.Library.

Core Features & Use Cases

  • Random file selection from Retrograde.Library and context gathering from related files
  • Generate exactly 5 targeted improvements across six quality axes: Elegance, Coherence, Style alignment, Dead code, Bad comments, Bad practices
  • Produce a structured Spotlight review ready for quick integration into reviews or walkthroughs

Quick Start

Run the spotlight on Retrograde.Library to receive five actionable improvements for a randomly selected file.

Frequently Asked Questions about spotlight

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

FAQPage Schema
How do I generate targeted C# code review improvements for underviewed files?

Targeted C# code review improvements are generated by analyzing random files alongside their base classes, sibling files, and common call sites to produce five actionable changes across six quality axes.

What quality axes does a structured static analysis spotlight cover for C# code?

A structured static analysis spotlight covers six quality axes: Elegance, Coherence, Style alignment, Dead code, Bad comments, and Bad practices, delivering five concrete improvements per reviewed C# file.

Can I use automated refactoring suggestions on any C# file in my library?

Automated refactoring suggestions can be applied to any C# file in Retrograde.Library, gathering context from related interfaces and call sites to propose five deterministic improvements ready for integration.

What's the best way to find dead code and bad practices in C# files without manual review?

Finding dead code and bad practices without manual review is done by running a spotlight that randomly selects a C# file, gathers contextual dependencies, and outputs five targeted improvements across six quality axes.

Does the spotlight approach work with existing C# code review workflows?

The spotlight approach works with existing C# code review workflows by producing a structured review document containing five actionable improvements that can be directly integrated into walkthroughs or pull request comments.

How many improvements does the spotlight generate per C# file analysis?

The spotlight generates exactly five deterministic improvements per analyzed C# file, evaluating code across six quality axes including elegance, coherence, style alignment, dead code, bad comments, and bad practices.