skills.rest
SeventeenthEarth
SeventeenthEarthCOMMUNITY
Explore all skills by this author →
GitHub

17th-code-analyzer

Analyze staged code changes for duplications, dead code, and optimization opportunities.

Updated Jan 23, 2026
Search Tags:#optimization#code-quality#analyze#dead-code#staged-changes#duplications#GPT-5.2-Codex
One-click install
npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-code-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 17th-code-analyzer
Source: https://github.com/SeventeenthEarth/glm-worker-mcp/tree/main/skills/17th-code-analyzer
Command: npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-code-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers identify duplications, dead code, and optimization opportunities in code changes, reducing risk before PRs.

Core Features & Use Cases

  • Code quality analysis of staged changes and surrounding code using GPT-5.2-Codex.
  • Duplication and dead code detection with actionable optimization suggestions.
  • Use Case: Before submitting a PR, run this Skill to surface refactoring opportunities across Go, Python, Dart, TypeScript, and JavaScript projects.

Quick Start

Use the 17th-code-analyzer to scan staged changes and surrounding code for duplications, dead code, and optimization opportunities.

Frequently Asked Questions about 17th-code-analyzer

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

FAQPage Schema
How do I find duplications and dead code in staged changes before a PR?▼

To detect dead code and duplications in staged production and test files, run an analyzer targeting staged changes and related modules in the same package. It reports findings and optimization opportunities across Go, Python, Dart, TypeScript, and JavaScript.

What is the best way to detect optimization opportunities in TypeScript and JavaScript projects?▼

Detect optimization opportunities in TypeScript and JavaScript by analyzing staged changes and surrounding code with GPT-5.2-Codex. It targets staged production and test files plus related modules to identify duplications and dead code.

Does this code quality analyzer work with Go, Python, and Dart staged files?▼

Yes, code quality analysis supports Go, Python, and Dart staged files. It targets staged production and test files plus related modules in the same package or directory, using GPT-5.2-Codex to identify duplications and dead code.

How do I analyze surrounding code context when reviewing staged changes?▼

Analyze surrounding code context by targeting staged production and test files plus related modules in the same package or directory. This approach evaluates the broader codebase context to surface duplications, dead code, and optimization opportunities.

Why should I scan for dead code and duplications before submitting a pull request?▼

Scan for dead code and duplications before submitting a pull request to reduce risk and improve code quality. Analyzing staged changes and surrounding code surfaces refactoring opportunities and optimization suggestions before merging.

Related Skills

Explore More Software Engineering Skills→
jkitchinjkitchin
34

tdd

Guide users through the Red-Green-Refactor cycle for Test-Driven Development.

Community
Intermediate
lpjhelderlpjhelder

ai-slop-cleaner

Remove dead code, duplication, and needless abstractions from scoped files.

Community
Intermediate
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced