code-quality-grader

Run deterministic lint, type, test, and security checks with pass/fail results.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/erhankaraarslan/agent_yazilim_ekibi --skill code-quality-grader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-grader
Source: https://github.com/erhankaraarslan/agent_yazilim_ekibi/tree/main/.claude/skills/code-quality-grader
Command: npx skills add https://github.com/erhankaraarslan/agent_yazilim_ekibi --skill code-quality-grader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized mechanism to evaluate code quality by running deterministic and model-based graders, reducing manual review effort and surfacing actionable results.

Core Features & Use Cases

  • Deterministic Lint, Type, and Test Checks: run linting, type checking, and test results to determine code health with clear PASS/FAIL signals.
  • Security Evaluation: perform security checks and vulnerability scans to surface high-risk issues during reviews.
  • Model-Based Quality Judgement: optional language-model based assessments for readability and API design when needed.

Quick Start

Run the code-quality-grader on your repository to perform automated linting, type checks, tests, and security checks. For example, trigger standard tooling in your project (lint, type-check, tests, and security scans) within your CI or local workflow.

Frequently Asked Questions about code-quality-grader

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

FAQPage Schema
How do I automate code quality checks in my CI pipeline?

Automated code review tools evaluate code health by running deterministic lint, type, and test graders to produce clear pass/fail signals, reducing manual review effort and surfacing actionable results during software development.

How do I run security checks and vulnerability scans during code reviews?

Security checks and vulnerability scans run during code reviews by executing automated security evaluations that surface high-risk issues, providing structured pass/fail results for integration into QA workflows.

Do I need standard tooling and configuration in my repository to run automated code quality grading?

Yes, automated code quality grading requires standard tooling and configuration to be present in the repository, as it triggers existing lint, type-check, test, and security scan tools to evaluate project health.

Can I use model-based judges for code readability and API design evaluation?

Yes, optional model-based judges provide language-model assessments for readability and API design, complementing deterministic lint, type, and test checks to offer a broader code quality evaluation.

What is the best way to standardize code quality evaluation across different languages and ecosystems?

Standardizing code quality evaluation across languages and ecosystems is done by running deterministic graders and optional model-based judges that cover linting, type checking, tests, and security checks, outputting structured pass/fail results.

Why does automated code grading require existing project configuration?

Automated code grading requires existing project configuration because it triggers standard tooling already set up in the repository to run lint, type-check, test, and security scans, ensuring accurate and context-aware pass/fail results.