code-quality
Improve TypeScript Code Quality
TypeScript and React teams need consistent quality checks before changes ship. This skill gives Claude, Codex, and Claude Code focused review standards and repair guidance.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "code-quality" from https://skillstore.io/skills/crazyswami-code-quality.md and its manifest at https://skillstore.io/api/skills/crazyswami-code-quality/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "code-quality". Review a React hook before a pull request.
Expected outcome:
- Identifies missing return types, absent cleanup, and incomplete error state handling.
- Recommends a typed result object, dependency review, and updated tests.
Using "code-quality". Fix type errors in a TypeScript component.
Expected outcome:
- Explains the root causes of unsafe types and missing null checks.
- Suggests safer type guards and preserves the component behavior.
Using "code-quality". Prepare a code quality checklist for a feature branch.
Expected outcome:
Provides a focused checklist covering TypeScript, naming, TSDoc, tests, Storybook, logging, and platform boundaries.
Security Audit
SafeStatic analysis flagged markdown backticks, one NODE_ENV example, and an anti-pattern heading. I found no executable shell, secret access, reconnaissance intent, or prompt injection.
Risk Factors
โ๏ธ External commands (23)
๐ Env variables (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/crazyswami-code-quality/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/crazyswami-code-quality?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/crazyswami-code-quality?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crazyswami-code-quality/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/crazyswami-code-quality.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
CrazySwami. (2026). code-quality security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crazyswami-code-quality/audits/8BibTeX citation
@techreport{crazyswami-crazyswami-code-quality-2026,
author = {CrazySwami},
title = {code-quality security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/crazyswami-code-quality/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "code-quality security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "CrazySwami"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/crazyswami-code-quality/audits/8"
identifiers:
- type: other
value: "skillstore:crazyswami-code-quality:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review Pull Requests
Check TypeScript, React, tests, Storybook, naming, and error handling before merge.
Set Team Standards
Use one checklist for strict typing, component structure, hooks, and platform abstraction rules.
Guide AI Code Fixes
Ask an AI assistant to repair type errors while keeping safe patterns and review expectations.
Try These Prompts
Review this TypeScript file for strict mode issues and list the safest fixes before editing.
Fix TypeScript errors in this component. Use unknown instead of any and add explicit return types where needed.
Review these React components for hook structure, memoization, TSDoc, naming, and Storybook coverage.
Audit this feature against our platform abstraction rules, code review checklist, and TypeScript strict mode requirements.
Best Practices
- Run the project type checker before final review when tooling is available.
- Prefer type guards, explicit return types, and unknown over unsafe assertions.
- Review components and hooks with tests, stories, error states, and cleanup behavior.
Avoid
- Do not use any or ts-ignore to hide unresolved type problems.
- Do not leave production console logs or unused variables in reviewed code.
- Do not bypass platform abstraction rules with direct platform-specific imports.
Frequently Asked Questions
What projects is this skill best for?
Does it automatically run linters?
Can it fix compiler errors?
Does it replace human review?
Can teams customize the standards?
Which AI tools can use it?
Developer Details
Author
CrazySwamiLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
d11af420e07cd866fe39cfa937efef3223896c06
Maintenance freshness
7/18/2026
Usage
4 downloads ยท 260 views
File structure
๐ SKILL.md