Code Quality

VerifiedSafe

Enforces a 500-line limit per file and mandatory JSDoc/Docstring comments for all functions and complex logic. Helps maintain consistent code quality and prevents overly long or under-documented files.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#code-quality#line-limit#comments#code-review#hallucination-prevention

Recommended for

Automated summary

This skill enforces strict code quality rules: a 500-line limit per file and mandatory comments for all functions and complex logic.

Strengths

  • Ensures reasonable file size, improving maintainability
  • Enforces systematic comments, enhancing readability
  • Prevents hallucinations by requiring file reading before edits

Limitations

  • The 500-line limit may be too rigid for configuration or generated files
  • Does not evaluate comment quality (only presence)
  • Requires CODE_STYLE.md to define detailed style rules
When to use it

Use this skill when you need to enforce a consistent codebase with short, well-documented files.

When not to use it

Avoid it for legacy or experimental code where flexibility outweighs strict compliance.

Security analysis

Safe
Quality score85/100

This skill enforces code quality rules (line limits, mandatory comments) using only Read, Grep, Glob, Edit, and Write tools. No destructive, network, or exfiltration commands are present. No hidden payloads or obfuscated instructions.

No concerns found

How this analysis is made

Examples

Review code quality of a file
Review the file src/utils/helpers.ts for code quality issues. Ensure it follows the 500-line limit and that every function has a JSDoc comment.
Enforce rule on new code
I'm about to write a new module. Before I start, check the code style rules and plan the file structure to stay under 500 lines per file with proper comments.
Fix comment violations
Find all functions in the project that are missing JSDoc or docstring comments and add them according to the project's style guidelines.

name: code-quality description: 코드 품질 규칙을 강제합니다. 500줄 제한과 주석 필수 규칙을 적용합니다. user-invocable: false allowed-tools: Read, Grep, Glob, Edit, Write agent: calab-plugin:code-reviewer agents: primary: calab-plugin:code-reviewer orchestration: write: [calab-plugin:code-reviewer] validate: [calab-plugin:validator] fix: [calab-plugin:reinforcer] review: [calab-plugin:code-reviewer, calab-plugin:validator]

Code Quality Skill

목적

코드 품질 규칙(줄 수 제한, 주석 필수)을 강제로 적용하여 일관된 코드 품질을 유지합니다.

핵심 규칙 (절대 무시 금지)

규칙 0: 할루시네이션 방지 (Anthropic 공식)

출처: docs.anthropic.com - 코드 작업 전 필수 확인

⚠️ 코드 수정 전 반드시:
1. 해당 파일 먼저 읽기 (추측 금지)
2. 코드베이스 스타일/컨벤션 파악
3. 확실하지 않으면 "확인 필요" 인정

절대 금지:

  • 열어보지 않은 파일 내용 추측
  • 확인 없이 코드 구조 주장
  • 근거 없는 수정 제안

규칙 1: 500줄 제한

모든 소스 파일은 반드시 500줄 이하로 작성

500줄 초과가 예상될 때:

  1. 먼저 파일을 분리할 계획을 세움
  2. 사용자에게 분리 방안 제안
  3. 승인 후 분리하여 작성

규칙 2: 주석 필수

모든 함수/메서드에 JSDoc 또는 Docstring 필수
복잡한 로직(조건문 3개 이상, 루프 2중 이상)에 설명 주석 필수

코드 생성 프로토콜

1. 사전 계획 (코드 작성 전)

단계:
1. CODE_STYLE.md 규칙 확인
2. 예상 줄 수 계산
3. 500줄 초과 예상 시 → 파일 분리 계획 수립
4. 함수 목록 작성 → 각 함수에 주석 계획

2. 코드 작성 중

규칙:
1. 함수 시작 전 → JSDoc/Docstring 먼저 작성
2. 복잡한 로직 전 → 설명 주석 작성
3. 100줄마다 → 현재 줄 수 체크
4. 200줄 도달 시 → 남은 코드 분리 검토

3. 코드 작성 후 (자체 검증)

체크리스트:
1. 총 줄 수 확인 (500줄 이하)
2. 모든 함수에 주석 존재
3. 복잡 로직에 설명 주석 존재
4. 위반 시 즉시 수정

출력 형식

500줄 초과 예상 시

============================================
[CODE QUALITY] 파일 분리 필요
============================================

예상 줄 수: ~450줄
최대 허용: 500줄

분리 제안:
1. user-service.ts (인증 로직) - ~150줄
2. user-repository.ts (DB 접근) - ~120줄
3. user-types.ts (타입 정의) - ~80줄
4. user-utils.ts (유틸리티) - ~100줄

============================================
이렇게 분리해서 작성할까요?

주석 작성 예시

TypeScript:

/**
 * 사용자 ID로 사용자 정보를 조회합니다.
 *
 * @param userId - 조회할 사용자의 고유 ID
 * @returns 사용자 객체 또는 존재하지 않으면 null
 * @throws DatabaseError 데이터베이스 연결 실패 시
 */
async function getUserById(userId: string): Promise<User | null> {

Python:

async def get_user_by_id(user_id: str) -> Optional[User]:
    """
    사용자 ID로 사용자 정보를 조회합니다.

    Args:
        user_id: 조회할 사용자의 고유 ID

    Returns:
        User 객체 또는 존재하지 않으면 None

    Raises:
        DatabaseError: 데이터베이스 연결 실패 시
    """

참조 파일

  • .claude/memory/CODE_STYLE.md - 상세 코드 스타일 규칙
  • .claude/memory/PROJECT_RULES.md - 프로젝트 규칙

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/code-quality-mma3jrwq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/code-quality-mma3jrwq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-quality-mma3jrwq/download' --output '.skill-downloads/code-quality-mma3jrwq/SKILL.md.part' && mv '.skill-downloads/code-quality-mma3jrwq/SKILL.md.part' '.skill-downloads/code-quality-mma3jrwq/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Grep, Glob, Edit, Write

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/code-quality-mma3jrwq/SKILL.md' && test -s '.skill-downloads/code-quality-mma3jrwq/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-quality' && cp -R '.skill-downloads/code-quality-mma3jrwq' '.claude/skills/code-quality'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/code-quality-mma3jrwq'

openskills read 'code-quality-mma3jrwq'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/code-quality-mma3jrwq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills