code-quality

Audit .NET and TypeScript source code for SOLID and DRY violations.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/piers-sinclair/Dostar --skill code-quality-piers-sinclair
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/piers-sinclair/Dostar/tree/main/.claude/skills/code-quality
Command: npx skills add https://github.com/piers-sinclair/Dostar --skill code-quality-piers-sinclair

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses technical debt and maintainability issues by performing a comprehensive, multi-layered audit of your codebase against industry-standard principles like SOLID, DRY, and clean architecture.

Core Features & Use Cases

  • Multi-Paradigm Auditing: Evaluates code against SOLID principles, separation of concerns, and modern .NET/TypeScript best practices.
  • Safety-First Remediation: Identifies issues with severity levels and requires explicit user confirmation before applying any changes, ensuring full control over refactoring.
  • TDD Regression: Enforces the creation of failing tests before applying fixes for bugs, ensuring robust regression protection.

Quick Start

Run the code-quality skill on the current directory to audit all files for quality issues and report findings.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I audit my TypeScript and .NET code for SOLID principle violations?

Run an automated code quality audit on your repository to identify SOLID principle violations, DRY pattern infractions, and architectural smells in TypeScript and .NET codebases.

What is the best way to identify architectural smells and performance bottlenecks in my codebase?

Perform a multi-paradigm audit that evaluates source code against separation of concerns and modern .NET or TypeScript best practices to detect architectural smells and performance bottlenecks.

Does the code quality audit require Git to analyze file diffs?

Yes, the code quality audit requires Git and standard shell utilities to analyze file diffs and generate actionable refactoring suggestions across .NET and TypeScript repositories.

How do I safely apply refactoring suggestions without breaking existing functionality?

Enforce a TDD regression approach by creating failing tests before applying fixes, and require explicit user confirmation before remediating identified code quality issues to ensure safe refactoring.

Can I run an automated code review to find nullability issues across my repository?

Yes, run an automated code review to audit source files for quality violations across .NET and TypeScript repositories, pinpointing nullability issues and architectural smells.