cham0287
- 6 skills
- 0 followers
- 15 hours ago last updated
- ▌ Task Workflow · cham0287 bundleRoute product and code tasks across one or more repositories from evidence intake to one reviewed plan and the authorized delivery boundary. Use when explicitly invoked with issues, documents, chat threads, commits, pull requests, screenshots, or natural-language requests to analyze, review, plan, implement, debug, QA, or continue work that may span repository or contract boundaries. Discover repository roles dynamically, preserve read-only requests, and coordinate implementation, verification, fresh review, optional specialist skills, PR packaging, and branch-owned CI repair. Do not use for routine development-server startup or isolated command execution.
- ▌ Backend Review · cham0287 bundleReview backend plans and code changes using evidence from the actual repository, callers, contracts, data writers, and runtime boundaries. Use for explicit backend review requests and for changes involving transactions, concurrency, permissions, public APIs, migrations, backfills, multi-model writes, external side effects, or new fallback and compatibility branches. Supports `quick`, `plan`, and `deep` modes. Do not trigger for formatting, imports, localized mechanical edits, documentation-only work, or tests that do not change production behavior.
- ▌ Check Change Impact · cham0287 bundleInspect a code diff, branch, commit, or PR and report its concrete blast radius with minimal prose. Use when asked what changes after merge or deploy, which APIs, requests, responses, data, jobs, external calls, shared consumers, schemas, or neighboring features are affected, or whether any impact surface was missed.
- ▌ Minimal Diff Review · cham0287 bundleReview a concrete code diff, commit, branch, or PR for overengineering, excessive defensive code, defensive branches caused by insufficient type narrowing, repository-pattern drift, unnecessary one-use abstractions, scope creep, and missed opportunities to keep the change minimal. Use after implementation and before commit, PR, or handoff whenever the user asks for a self-review, minimal diff, overengineering check, defensive-code check, type-narrowing check, unusual-pattern check, inline-helper check, scope check, or says to keep only what must change. Also trigger on recurring Korean requests such as 오버엔지니어링, 과도한 방어코드, 타입을 제대로 좁히지 않아 생긴 방어로직, 불필요한 null/undefined 방어, 특이한 패턴, inline으로 충분한 함수, 작업 범위 이탈, 최소 diff, or 꼭 고쳐야 하는 것만. This is a focused read-only review lens, not a general bug hunt or refactoring pass; do not edit files unless the user explicitly asks after seeing the findings.
- ▌ React Code Design Review · cham0287 bundleReview React and React Native code structure using contextual rules for ownership, data access, UI-to-code mapping, composition, naming, and accessibility. Use when a user asks to review, refactor, or design React code or a component-heavy diff. Inspect real call sites and repository conventions before reporting findings. Do not use for visual styling critique, broad application architecture, or performance review without structural evidence.
- ▌ Create Prompt Log Artifact · cham0287 bundleCreate a concise, self-contained HTML artifact containing only the prompts the user directly entered in one Codex task. Use when the user asks to view, export, collect, review, or share their prompts from the current or a specified Codex task/session, especially requests for a prompt log, prompt history, or user-input-only artifact.