aico-code-review

Request structured code review to catch correctness, security, performance, and readability issues. Reviews should happen early and often. Use this skill when: - Completing a task and need quality check - After major feature implementation - Before merging to main branch - When stuck and need fresh perspective on code - User asks for "code review", "review my code", "check my code" - Subagent-driven workflow needs spec compliance or quality review Review categories: Correctness, Tests, Security, Performance, Readability, Error Handling Severity levels: Critical (fix now), Important (fix before proceeding), Minor (note for later)

설치로 이동

저장소: yellinzero/aico
최근 소스 활동: 2026년 1월 13일 05:03
감지된 SKILL.md 언어: 영어
스타: 1
포크: 0

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/yellinzero/aico --skill aico-code-review

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

검색으로 돌아가기 설치로 돌아가기

aico-backend-implement

Execute backend task implementation with TDD. Read task file, execute steps, verify each, update status. Use this skill when: - User asks to "implement task/plan", "start implementation", "execute plan", or "start coding" - Have task file (story-* or standalone-*) ready to execute - User asks to "use TDD", "write test first", or "test-driven" - User asks to "write tests", "add tests", "create tests" - Fixing bugs (write failing test first) TDD Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST TDD Cycle: RED (failing test) → Verify fails → GREEN (minimal code) → Verify passes → REFACTOR Prerequisites: - Task file in docs/reference/backend/tasks/ (story-* or standalone-*) - Read constraints.md and design spec before coding Flow: Read Task → Read Constraints → Execute Steps → Verify → Test → Update Status

2026-02-12

aico-backend-plan

Create or enhance backend tasks with detailed implementation steps. Supports TWO modes: MODE A: Enhance existing task (add detailed steps to task in file) MODE B: Create new standalone task file (can contain single or multiple tasks) IMPORTANT: This skill creates MICRO-LEVEL atomic steps, NOT macro architecture plans. For architecture planning or feature scoping, use EnterPlanMode instead. Use this skill when: - Running /backend.plan command - User asks for "atomic steps", "step-by-step plan with verification" - Have a specific task and need implementation steps - User wants to create a standalone task file (not from story) - Need granular steps: Types → DB → Repository → Service → API → Tests DO NOT use for: - Architecture planning (use EnterPlanMode) - General development planning - Feature scoping or estimation Output: - MODE A: Update specific task section in file with Implementation Steps - MODE B: Create new standalone-{name}.md file with one or multiple tasks

2026-02-12

aico-backend-task-breakdown

Break down PM story into organized tasks in a single file following LAYERED ARCHITECTURE order: Types → Database → Repository → Service → API → Tests. UNIQUE VALUE: Creates single task file (story-{name}.md) containing all tasks for a story. Tasks are ordered by backend architecture layers. Use this skill when: - Running /backend.tasks command - User asks to "break down story", "create backend tasks", "split into tasks" - Have story at docs/reference/pm/stories/ and need organized task breakdown - Need tasks ordered by backend architecture layers (not random order) - Starting backend work and want organized task list Task order is CRITICAL: Types → Database → Repository → Service → API → Tests Output: Create single file docs/reference/backend/tasks/story-{name}.md with all tasks

2026-02-12

이 저장소의 모든 Skills 보기

name

aico-code-review

description

Code Review

When to Request Review

Mandatory:

After completing each task
After implementing major feature
Before merge to main

Optional:

When stuck (fresh perspective)
Before refactoring
After fixing complex bug

Review Checklist

Category	Check
Correctness	Does it do what it should?
Tests	Are there tests? Do they pass?
Security	Any vulnerabilities?
Performance	Any obvious bottlenecks?
Readability	Is code clear and maintainable?
Error Handling	Are errors handled properly?

Issue Severity

Severity	Action
Critical	Fix immediately, blocks progress
Important	Fix before proceeding
Minor	Note for later, can proceed

Review Output Template

## Code Review: [Feature/Task Name]

### Files Modified

- `path/to/file.ts` - [what changed]

### Issues

**Critical:**

- [ ] [Issue description]

**Important:**

- [ ] [Issue description]

**Minor:**

- [ ] [Issue description]

### Assessment

- [ ] Ready to proceed
- [ ] Needs fixes (see issues above)

Key Rules

ALWAYS review after each task completion
MUST fix Critical issues immediately
MUST fix Important issues before proceeding
Minor issues can be noted for later
If reviewer is wrong, push back with technical reasoning

Common Mistakes

❌ Skip review because "it's simple" → ✅ Review everything
❌ Ignore Critical issues → ✅ Fix immediately
❌ Proceed with Important issues → ✅ Fix first

aico-code-review

소스 정보

설치 방법

소스 파일 검토

이 저장소의 다른 Skills

이 저장소의 다른 Skills

Code Review

When to Request Review

Review Checklist

Issue Severity

Review Output Template

Key Rules

Common Mistakes

Code Review

When to Request Review

Review Checklist

Issue Severity

Review Output Template

Key Rules

Common Mistakes