papercuts

Scans project files for code quality issues like TODOs and dead code.

3|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Pixley-Growth/cal-plugin --skill papercuts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: papercuts
Source: https://github.com/Pixley-Growth/cal-plugin/tree/main/skills/papercuts
Command: npx skills add https://github.com/Pixley-Growth/cal-plugin --skill papercuts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Papercuts identifies and optionally resolves small code quality issues, ensuring the codebase remains clean and maintainable without extensive manual oversight.

Core Features & Use Cases

  • Automated Code Hygiene: Scan for TODOs, dead code, naming issues, and error swallowing without human intervention.
  • Optional Fixing: With a single command, fix identified issues with manual approval.
  • Scalable: Intended for any project directory, scanning current project files specifically.
  • Language-Agnostic: Detects issues in TypeScript/JavaScript, Swift, and other common programming languages.

Quick Start

Scan your codebase for hygiene issues by using the command /cal:papercuts.

Frequently Asked Questions about papercuts

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

FAQPage Schema
How do I automatically scan my codebase for TODOs and dead code?

To automatically scan for TODOs and dead code, run the `/cal:papercuts` command within your project directory to identify minor code quality issues across your current files without manual oversight.

Can I automatically fix naming inconsistencies and error swallowing in TypeScript or Swift?

Yes, you can optionally fix naming inconsistencies and error swallowing in TypeScript, JavaScript, and Swift files by running the automated scan and applying suggested corrections with manual approval.

What is the best way to maintain code hygiene across multiple programming languages?

Maintaining code hygiene across multiple languages is best achieved through automated code scanning that detects issues like dead code and inconsistent naming in various programming languages within your project directory.

Does this automated code scanning require language-specific configuration to detect issues?

No, automated code scanning does not require language-specific configuration or manual file processing, as it performs file and line analysis to detect issues across common programming languages natively.

How do I resolve minor code quality issues after an automated scan?

To resolve minor code quality issues after an automated scan, use the optional fixing feature which allows you to apply corrections to identified issues with a single command and manual approval.