codeninja-level-3

Review TypeScript codebases for strict type safety and code smells.

5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Rikinshah787/clawarmy --skill codeninja-level-3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codeninja-level-3
Source: https://github.com/Rikinshah787/clawarmy/tree/main/.cursor/skills/codeninja-level-3
Command: npx skills add https://github.com/Rikinshah787/clawarmy --skill codeninja-level-3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the highest standards of code quality, type safety, and maintainability, preventing subtle bugs and technical debt in critical codebases.

Core Features & Use Cases

  • Rigorous Code Analysis: Identifies and rejects code smells, anti-patterns, and potential bugs.
  • Strict Type Safety Enforcement: Mandates explicit typing and safe type assertions in TypeScript.
  • Refactoring Suggestions: Proactively suggests improvements for cleaner, more efficient code.
  • Use Case: Reviewing a new feature for a financial transaction system where even minor errors could have significant consequences.

Quick Start

Use the codeninja-level-3 skill to review the attached TypeScript file for strictness violations.

Frequently Asked Questions about codeninja-level-3

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

FAQPage Schema
How do I perform a strict TypeScript code review to enforce maximum type safety?

Strict TypeScript code review enforces explicit typing and safe type assertions by analyzing codebases for code smells, anti-patterns, and potential bugs. It targets high-assurance software development by mandating zero tolerance for type safety violations and suggesting ruthless refactoring.

What is elite code review and when do I need it for critical production code?

Elite code review provides rigorous analysis for critical production code and library development by ensuring maximum adherence to best practices. It is needed when building high-assurance software like financial transaction systems where even minor errors have significant consequences.

Can I use automated refactoring suggestions to eliminate code smells in TypeScript?

Automated refactoring suggestions proactively identify code smells and anti-patterns in TypeScript codebases, then propose cleaner, more efficient code improvements. This ensures maintainability and robustness through detailed analysis and explicit typing enforcement.

Does strict code review work for library development requiring zero tolerance for anti-patterns?

Strict code review works for library development by enforcing zero tolerance for anti-patterns and code smells through detailed analysis. It ensures code quality, maintainability, and robustness by mandating explicit typing and rejecting potential bugs.

What's the best way to review TypeScript files for strictness violations in high-assurance software?

Reviewing TypeScript files for strictness violations involves attaching the file for analysis and enforcing maximum adherence to best practices. The review targets mandatory type safety, explicit typing, and ruthless refactoring to prevent subtle bugs and technical debt.

Why does strict type safety enforcement matter for preventing technical debt in critical codebases?

Strict type safety enforcement matters because it prevents subtle bugs and technical debt in critical codebases by mandating explicit typing and rejecting unsafe type assertions. This ensures long-term maintainability and robustness for high-assurance software development.