enterprise-code-quality

Use when auditing, reviewing, refactoring, or planning improvements to application or infrastructure code that needs maintainability, typed boundaries, tests…

Skill by priyanshuchawda

IndexedMIT★ 1

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/priyanshuchawda-enterprise-code-quality

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when auditing, reviewing, refactoring, or planning improvements to application or infrastructure code that needs maintainability, typed boundaries, tests, or simpler architecture.

Use cases: devops

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/enterprise-code-quality

What's inside

Skill name: enterprise-code-quality
Description: Use when auditing, reviewing, refactoring, or planning improvements to application or infrastructure code that needs maintainability, typed boundaries, tests, or simpler architecture.
License: MIT
Metadata: internal: true
Instructions: 25 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Enterprise Code Quality

## Standards

- Prefer small focused files with one clear responsibility.
- Use typed contracts and schema validation at external boundaries.
- Prefer clear names and simple control flow over clever abstractions.
- Avoid god files, vague helpers, dead code, and duplicated logic.
- Keep error handling explicit and useful without leaking secrets.
- Refactor only with tests before or alongside the change.

## Review Checklist

- File size and responsibility boundaries.
- API, CLI, config, and database input validation.
- Test coverage for changed behavior.
- Data flow across server/client or trust boundaries.
- Duplicated logic that can be safely consolidated.
- Overengineering that hides simple domain logic.

## Output Style

Findings should include severity, file evidence, why it matters, and the smallest practical recommendation.

From priyanshuchawda/codeaudit, MIT.

Signals

Stars: 1
Forks: 0
Open issues: 0
Last commit (this folder): May 4, 2026 (5 months ago)
Last release: May 4, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/priyanshuchawda/codeaudit
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from priyanshuchawda

Cite this page

enterprise-code-quality skill. Agent Mart. https://agentmart.dev/skills/priyanshuchawda-enterprise-code-quality (last updated 2026-10-24)