ln-511-code-quality-checker（ln 511 代码质量检查器） Skills下载安装命令和教程

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：ln-511-code-quality-checker（ln 511 代码质量检查器）
来源仓库：https://github.com/levnikolaevich/claude-code-skills
仓库路径：skills/ln-511-code-quality-checker
安装命令：
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-511-code-quality-checker
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-511-code-quality-checker

简介

用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。

支持基于关键词、任务场景或来源线索进行信息检索与筛选。
通过 npx skills add 命令从指定 GitHub 仓库安装使用。
安装前需确认权限范围、维护状态及是否涉及联网或文件操作。
ln-511-code-quality-checker 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

Paths: File paths (shared/, references/, ../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. If shared/ is missing, fetch files via WebFetch from https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.

Code Quality Checker

Type: L3 Worker Category: 5XX Quality

Analyzes Done implementation tasks with quantitative Code Quality Score based on metrics, MCP Ref validation, and issue penalties.

Inputs

Input	Required	Source	Description
`storyId`	Yes	args, git branch, kanban, user	Story to process

Resolution: Story Resolution Chain. Status filter: In Progress, To Review

MANDATORY READ: Load shared/references/mcp_tool_preferences.md and shared/references/mcp_integration_patterns.md - use hex-graph as the primary path for clone, architecture, and semantic quality evidence when the project is indexed. Fall back to Grep/Read only when graph is unavailable or unsupported.

Purpose & Scope

Load Story and Done implementation tasks (exclude test tasks)
Calculate Code Quality Score using metrics and issue penalties
MCP Ref validation: Verify optimality, best practices, and performance via external sources
Check for DRY/KISS/YAGNI violations, architecture boundary breaks, security issues
Produce quantitative verdict with structured issue list; never edits Linear or kanban

Code Metrics

Metric	Threshold	Penalty
Cyclomatic Complexity	≤10 OK, 11-20 warning, >20 fail	-5 (warning), -10 (fail) per function
Function size	≤50 lines OK, >50 warning	-3 per function
File size	≤500 lines OK, >500 warning	-5 per file
Nesting depth	≤3 OK, >3 warning	-3 per instance
Parameter count	≤4 OK, >4 warning	-2 per function

Code Quality Score

Formula: Code Quality Score = 100 - metric_penalties - issue_penalties

Issue penalties by severity:

Severity	Penalty	Examples
high	-20	Security vulnerability, O(n²)+ algorithm, N+1 query
medium	-10	DRY violation, suboptimal approach, missing config
low	-3	Naming convention, minor code smell

Score interpretation:

Score	Status	Verdict
90-100	Excellent	PASS
70-89	Acceptable	CONCERNS
<70	Below threshold	ISSUES_FOUND

Issue Prefixes

Prefix	Category	Default Severity	MCP Ref
SEC-	Security (auth, validation, secrets)	high	—
SEC-DESTR-	Destructive ops (guards: DB, FS, MIG, ENV, FORCE)	high/medium	—
PERF-	Performance (algorithms, configs, bottlenecks)	medium/high	✓ Required
MNT-	Maintainability (DRY, SOLID, complexity, dead code)	medium	—
ARCH-	Architecture (layers, boundaries, patterns, contracts)	medium	—
BP-	Best Practices (implementation differs from recommended)	medium	✓ Required
OPT-	Optimality (better approach exists for this goal)	medium	✓ Required

OPT- subcategories:

Prefix	Category	Severity
OPT-OSS-	Open-source replacement available	medium (high if >200 LOC)

ARCH- subcategories:

Prefix	Category	Severity
ARCH-LB-	Layer Boundary: I/O outside infra, HTTP in domain	high
ARCH-TX-	Transaction Boundaries: commit() in 3+ layers, mixed UoW ownership	high (CRITICAL if auth/payment)
ARCH-DTO-	Missing DTO (4+ params without DTO), Entity Leakage (ORM entity in API response)	medium (high if auth/payment)
ARCH-DI-	Dependency Injection: dependencies not replaceable for testing (direct instantiation, no injection mechanism). Exception: small scripts/CLIs where params/closures suffice → skip	medium
ARCH-CEH-	Centralized Error Handling: errors silently swallowed, stack traces leak to prod, no consistent error logging. Exception: 50-line scripts → downgrade to LOW	medium (high if no handler at all)
ARCH-SES-	Session Ownership: DI session + local session in same module	medium
ARCH-AI-SEB	Side-Effect Breadth: 3+ side-effect categories in one leaf function. Conflict Resolution: orchestrator/coordinator functions (imports 3+ services AND delegates sequentially) are EXPECTED to have multiple categories — do NOT flag SEB	medium
ARCH-AI-AH	Architectural Honesty: read-named function with write side-effects	medium
ARCH-AI-FO	Flat Orchestration: leaf service imports 3+ other services. Orchestrator imports are expected — do NOT flag	medium
ARCH-EVENT-	Event Channel Consistency: publisher/subscriber name mismatch (MISMATCH), orphaned channel with no counterpart (ORPHAN)	high (mismatch), medium (orphan)

PERF- subcategories:

Prefix	Category	Severity
PERF-ALG-	Algorithm complexity (Big O)	high if O(n²)+
PERF-CFG-	Package/library configuration	medium
PERF-PTN-	Architectural pattern performance	high
PERF-DB-	Database queries, indexes	high

MNT- subcategories:

Prefix	Category	Severity
MNT-DC-	Dead code: replaced implementations, unused exports/re-exports, backward-compat wrappers, unsupported aliases	medium (high if public API)
MNT-DRY-	DRY violations: duplicate logic across files	medium
MNT-GOD-	God Classes: class with >15 methods or >500 lines (not just file size)	medium (high if >1000 lines)
MNT-SIG-	Method Signature Quality: boolean flag params, unclear return types, inconsistent naming, >5 optional params	low
MNT-ERR-	Error Contract inconsistency: mixed raise + return None in same service	medium

When to Use

All implementation tasks in Story status = Done
Before tech debt cleanup and inline agent review

Workflow (concise)

MANDATORY READ: Load shared/references/input_resolution_pattern.md

Resolve storyId: Run Story Resolution Chain per guide (status filter: [In Progress, To Review]).
Load Story (full) and Done implementation tasks (full descriptions) via Linear; skip tasks with label "tests".
Collect changed files (changed_files[]): MANDATORY READ: Load shared/references/git_scope_detection.md

- IF invoked by ln-510: use changed_files[] from coordinator context → proceed to Enrich step in guide - IF invoked standalone: run full algorithm from guide

Two-Layer Detection (MANDATORY): MANDATORY READ: Load shared/references/two_layer_detection.md All threshold-based findings require Layer 2 context analysis. Layer 1 finding without Layer 2 = NOT a valid finding. Before reporting any metric violation, ask: "Is this violation intentional or justified by design?" See Exception column in metrics below.
Calculate code metrics:

- Cyclomatic Complexity per function (target ≤10; Exception: enum/switch dispatch, state machines, parser grammars → downgrade to LOW) - Function size (target ≤50 lines; Exception: orchestrator functions with sequential delegation) - File size (target ≤500 lines; Exception: config/schema/migration files, generated code) - Nesting depth (target ≤3) - Parameter count (target ≤4; Exception: builder/options patterns)

MCP Ref Validation (MANDATORY for code changes — SKIP if --skip-mcp-ref flag passed): MANDATORY READ: Load shared/references/research_tool_fallback.md Fast-track mode: When invoked with --skip-mcp-ref, skip this entire step (no OPT-, BP-, PERF- checks). Proceed directly to step 6 (static analysis). This reduces cost from ~5000 to ~800 tokens while preserving metrics + static analysis coverage. Level 1 — OPTIMALITY (OPT-): Level 2 — BEST PRACTICES (BP-): Level 3 — PERFORMANCE (PERF-): Triggers for MCP Ref validation:

- Extract goal from task (e.g., "user authentication", "caching", "API rate limiting") - Research alternatives: ref_search_documentation("{goal} approaches comparison {tech_stack} 2026") - Compare chosen approach vs alternatives for project context - Flag suboptimal choices as OPT- issues - Research: ref_search_documentation("{chosen_approach} best practices {tech_stack} 2026") - For libraries: query-docs(library_id, "best practices implementation patterns") - Flag deviations from recommended patterns as BP- issues - PERF-ALG: Analyze algorithm complexity (detect O(n²)+, research optimal via MCP Ref) - PERF-CFG: Check library configs (connection pooling, batch sizes, timeouts) via query-docs - PERF-PTN: Research pattern pitfalls: ref_search_documentation("{pattern} performance bottlenecks") - PERF-DB: Check for N+1, missing indexes via query-docs(orm_library_id, "query optimization") - New dependency added (package.json/requirements.txt changed) - New pattern/library used - API/database changes - Loops/recursion in critical paths - ORM queries added

Analyze code for static issues (assign prefixes): MANDATORY READ: Load shared/references/clean_code_checklist.md, shared/references/destructive_operation_safety.md

- For large code files, use outline(file_path) before targeted reads. - SEC-: hardcoded creds, unvalidated input, SQL injection, race conditions - SEC-DESTR-: unguarded destructive operations — use code-level guards table from destructive_operation_safety.md (loaded above). Check all 5 guard categories (DB, FS, MIG, ENV, FORCE). - MNT-: DRY violations (MNT-DRY-: duplicate logic), dead code (MNT-DC-: per checklist), complex conditionals, poor naming - MNT-DRY- cross-story hotspot scan: Grep for common pattern signatures (error handlers: catch.*Error|handleError, validators: validate|isValid, config access: getSettings|getConfig) across ALL src/ files (count mode). If any pattern appears in 5+ files, sample 3 files (Read 50 lines each) and check structural similarity. If >80% similar → MNT-DRY-CROSS (medium, -10 points): Pattern X duplicated in N files — extract to shared module. - MNT-DRY- preferred (hex-graph): If hex-graph indexed, use audit_workspace(path=scan_path, verbosity="minimal", limit=5, clone_member_limit=3). Each clone group with 2+ members in different files = MNT-DRY-CROSS. Raise limits only when the bounded preview is insufficient. Use returned hotspot and clone context for priority. Fall back to Grep pattern scan above if hex-graph unavailable. - MNT-DC- cross-story unused export scan: For each file modified by Story, count export declarations. Then Grep across ALL src/ for import references to those exports. Exports with 0 import references → MNT-DC-CROSS (medium, -10 points): {export} in {file} exported but never imported — remove or mark internal. - OPT-OSS- cross-reference ln-645 (static, fast-track safe): IF docs/project/.audit/ln-640/*/645-open-source-replacer*.md exists (glob across dates, take latest), check if any HIGH-confidence replacement matches files changed in current Story. IF match found → create OPT-OSS-{N} issue with module path, goal, recommended package, confidence, stars, license from ln-645 report. Severity: high if >200 LOC, medium otherwise. This check reads local files only — no MCP calls — runs even with --skip-mcp-ref. - ARCH-: layer violations, circular dependencies, guide non-compliance - ARCH-LB-: layer boundary violations (HTTP/DB/FS calls outside infrastructure layer) - ARCH-TX-: transaction boundary violations (commit() across multiple layers) - ARCH-DTO-: missing DTOs (4+ repeated params), entity leakage (ORM entities returned from API) - ARCH-DI-: direct instantiation in business logic (no DI container or mixed patterns) - ARCH-CEH-: centralized error handling absent or bypassed - ARCH-SES-: session ownership conflicts (DI + local session in same module) - ARCH-AI-SEB: side-effect breadth (3+ categories in one leaf function; orchestrator functions exempt — see Conflict Resolution in table above) - ARCH-AI-AH: architectural honesty (read-named function with hidden writes) - ARCH-AI-FO: flat orchestration (leaf service importing 3+ services; orchestrator imports exempt) - ARCH-EVENT-: event channel mismatch — Grep for NOTIFY|pg_notify|\.publish\(|\.emit\( (publishers) and LISTEN|\.subscribe\(|\.on\( (subscribers) in changed_files[]. Cross-reference channel name strings. - MNT-GOD-: god classes (>15 methods or >500 lines per class) - MNT-SIG-: method signature quality (boolean flags, unclear returns) - MNT-ERR-: error contract inconsistency (mixed raise/return patterns in same service)

Calculate Code Quality Score:

- Start with 100 - Subtract metric penalties (see Code Metrics table) - Subtract issue penalties (see Issue penalties table)

Output verdict with score and structured issues. MANDATORY READ: Load references/output_schema.md Format output per schema. Add Linear comment with findings.

Critical Rules

Read guides mentioned in Story/Tasks before judging compliance.
MCP Ref validation: For ANY architectural change, MUST verify via ref_search_documentation before judging.
Context7 for libraries: When reviewing library usage, query-docs to verify correct patterns.
Language preservation in comments (EN/RU).
Do not create tasks or change statuses; caller decides next actions.

Runtime Summary Artifact

MANDATORY READ: Load shared/references/quality_summary_contract.md, shared/references/quality_worker_runtime_contract.md

Runtime profile:

family: quality-worker
worker: ln-511
summary kind: quality-worker
payload fields used by coordinators: worker, status, verdict, score, issues, warnings

Invocation rules:

standalone: omit runId and summaryArtifactPath
managed: pass both runId and exact summaryArtifactPath
always write the validated summary before terminal outcome

Definition of Done

Story and Done implementation tasks loaded (test tasks excluded)
Code metrics calculated (Cyclomatic Complexity, function/file sizes)
MCP Ref validation completed (OPT-, BP-, PERF- categories)
ARCH- subcategories checked (LB, TX, DTO, DI, CEH, SES, EVENT); MNT- subcategories checked (DC, DRY, GOD, SIG, ERR)
Issues identified with prefixes and severity, sources from MCP Ref/Context7
Code Quality Score calculated
Output formatted per references/output_schema.md
Linear comment posted with findings

Reference Files

Git scope detection: shared/references/git_scope_detection.md
Code metrics: references/code_metrics.md (thresholds and penalties)
Guides: docs/guides/
Templates for context: shared/templates/task_template_implementation.md
Clean code checklist: shared/references/clean_code_checklist.md
Research tool fallback: shared/references/research_tool_fallback.md

Version: 5.1.0 Last Updated: 2026-03-15

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

39.32%

按下载量换算841

Claude

27.7%

按下载量换算592

Cursor

20%

按下载量换算428

Gemini CLI

9.53%

按下载量换算204

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API，使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果，不能写成本站确认安全。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/levnikolaevich/claude-code-skills

SKILL.md 来源

github.com

/levnikolaevich/claude-code-skills/tree/main/skills/ln-511-code-quality-checker

skills-sh

skills.sh

/levnikolaevich/claude-code-skills/ln-511-code-quality-checker

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

ln-510-test-planner（ln 510 测试计划员）

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据，避免为了通过测试而改坏真实逻辑；涉及浏览器或外部服务时，应区分本地模拟、测试环境和生产环境。

下一个 Skill

ln-511-test-researcher（ln 511 测试研究员）

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据，避免为了通过测试而改坏真实逻辑；涉及浏览器或外部服务时，应区分本地模拟、测试环境和生产环境。