clean-code

Detect and remove unused Swift code using Periphery.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/vjr2005/Challenge --skill clean-code-vjr2005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/vjr2005/Challenge/tree/main/.claude/skills/clean-code
Command: npx skills add https://github.com/vjr2005/Challenge --skill clean-code-vjr2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and removes unused code using Periphery to maintain a clean, safe Swift codebase and reduce dead code and potential defects.

Core Features & Use Cases

  • Dead code detection with Periphery
  • Before-release cleanup workflow
  • Guided removal with tests and mocks verification

Quick Start

Run Periphery analysis to identify unused declarations and begin the cleanup workflow.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I detect and remove dead code in a Swift project?

Dead code detection in a Swift project is performed by scanning for unused declarations with Periphery, searching for references, and guiding removal while verifying tests and mocks remain intact.

What is the best way to run a before-release cleanup workflow for Swift modules?

A before-release cleanup workflow for Swift modules applies Periphery static analysis to identify and remove unused code deterministically across modules, ensuring a safe codebase before deployment.

How does Periphery static analysis handle unused code across multiple Swift modules?

Periphery static analysis handles unused code across multiple Swift modules by performing a deterministic scan that searches for references and identifies declarations that can be safely removed project-wide.

When should I use Periphery for dead code removal instead of manual refactoring?

Use Periphery for dead code removal during periodic maintenance or before releases when you need a deterministic, automated scan across modules rather than relying on manual, error-prone refactoring.