Use when writing, reviewing, or modifying source code in any language (Java / TypeScript / JavaScript / Dart / Python / Kotlin / Go / Vue / React ็ญ). ่ทจ่ฏญ่จ้็จ็ผ็ ้ๅพ 7 ๆก + ๆณจ้ไธๆกฃ,่ฏญ่จไธๅฑ skill (java-coding-standards / korepos-backend-service ็ญ) ๅจๆญคๅบ็กไธๅ ๅ ใMUST ่ชๅจ่งฆๅ,ไธ้็จๆทๆพๅผ่ฆๆฑใ
Use when writing, reviewing, or modifying any Java code. You MUST follow these mandatory rules at all times. Apply automatically without being asked. ้็จๆกๆฌพ่ง coding-standards-common๏ผๆฌๆไปถไป ๅ Java ็ฌๅ ่งๅ๏ผ้ฟ้ๅทดๅทด้ปๅฑฑ็ๅผบๅถ้กน็ Java ไธๅฑ้จๅ๏ผใ
Use when the user asks to commit code or generate a commit message AND the staged diff is non-trivial (>2 files, >30 net lines, or contains new/renamed/deleted files). For trivial commits (โค2 files, โค30 lines, only modifications to existing files) skip this skill and write a clear `git commit` message directly โ `hooks/check-git-commit-skill.js` enforces the same threshold at the Bash layer (only blocks `git commit` when staged diff exceeds it). Compose the message from the current session's edit intent first; only re-read diffs to cover gaps. Automatic stage/commit/push applies ONLY to the team-standards plugin source repository, never to business projects that merely install this plugin.
Use BEFORE answering single-service backend questions about table relations / ER / SQL / state transitions / atomic capabilities or project-level technical pain points (subprocess, concurrency, perf, external deps); BEFORE Write/Edit any .md describing such content (anywhere โ docs/, ai-docs/, scenarios/, work-log/). Auto-append candidates to `_candidates.md` after investigation discovers reusable facts, or when same tech concern raised โฅ3 rounds in one session. Knowledge graph ownership = investigated service, not cwd. Detailed triggers (7 BLOCKING conditions) and scope boundaries listed in `## BLOCKING ๅผบ่งฆๅๆธ ๅ` section of SKILL.md body.
Use when writing or modifying code that integrates an LLM or builds an agent โโ imports langchain4j / spring-ai / openai / anthropic ็ญ SDK๏ผๅฎไน @Tool / AiService / function-calling ๅทฅๅ ท๏ผๆผ่ฃ prompt๏ผ่งฃๆ LLM ่พๅบใๅจ coding-standards-common ไนไธๅ ๅ ็ LLM/Agent ้ๆ็ผ็ ้ๅพ๏ผ็กฎๅฎๆงไผๅ ใLLM ่พๅบๅฝไธๅฏไฟกๅ ฅๅใๆจก็ณโ็ปๆๅ็จๅๆงๆไธพใ็บฆๅฎๅไธๆฅๆบใๅทฅๅ ทๆ่ฟฐๆฏ่ฟ่กๆถๅฅ็บฆใAgent ๅพช็ฏๅฟ ้กปๅ ๅบใไธไธๆ็ฑไปฃ็ ๆณจๅ ฅใMUST ่ชๅจ่งฆๅ๏ผๅ ๆปก่ถณ coding-standards-common ๅ่ตฐๆฌ skillใ
ๅฝ็จๆท่ฆๆฑใๆถๆๆฃๆฅใใlintใใๆฃๆตๆถๆ่ฟ่งใๆถ่งฆๅ๏ผๅฝๅฏน Flutter ้กน็ฎ็ presentation/domain/data/infrastructure ๅฑไปฃ็ ๆง่ก Edit/Write ๅ่ชๅจ่งฆๅไธๆฌก่ฝป้ๆฃๆฅใ
You MUST invoke this skill the moment a user reports a bug, describes an error/exception, asks you to investigate or analyze a problem, or mentions writing a bug analysis document. Trigger phrases include: 'there is a bug', 'this is broken', 'why is X happening', 'investigate this issue', 'analyze the root cause', 'we have an OOM/NPE/timeout', 'help me debug'. Invoke BEFORE starting any investigation, root cause analysis, or creating any file under docs/bug/. Pairs with doc-index-required โ always invoke that skill too.
Use when applying any bug fix, alignment correction, redundant-code removal, OR adding missing logic to align with upstream/cloud during integration/่่ฐ phase. Trigger when: (1) design-doc-required has routed the change to ใ็ฌฌๅยทไบๆญฅ๏ผ่ฝป้ไฟฎ่ฎขๆตๆฐดใ branch, (2) user describes the change as 'fix bug', 'align with cloud/upstream', 'add missing piece', 'ไฟฎ bug', 'ๅฏน้ฝไบ็ซฏ', 'ๅ ๅไฝ', 'ไฟฎๆญฃๅฎ็ฐ', 'ๆนๅๆญฃ็กฎ้ป่พ', '่กฅไธๆผๆ็้ป่พ', '่กฅ็ผบๆผ', or (3) about to Edit/Write source code with intent of replacing existing erroneous logic OR adding alignment code that was missed in previous iterations. **ๆณจ้็บข็บฟไธๅจๆฌ skill ๅฎไน** โ ๅฏไธ่งๅๆบๆฏ coding-standards-common ยง5.4 + ยง5.4.1(common ่งฆๅ้กบๅบๆฉไบๆฌ skill,ไธไผๆผ)ใๆฌ skill ๅชๆฟๆ bug ไฟฎๅคๆ็ฌๆ็ๅบ็จๅฑๆๅผ:v1.17 ๆนๅๅ่ฝฌ็ๅๅฒ่ๆฏใๆจ่ๅๆณ dart ไปฃ็ ็คบไพใๆๆพไฝ็ฝฎใ้็จ่ๅด็ฉ้ตใ้ๅฐๅญ้ [DEPRECATED]/[ADDED] ๆณจ้้กบๆๆธ ็็่พน็ใ็บข่ฒ่ญฆๅๅฏน็ ง่กจใ