sskim91/dotfiles

codex-changelog-review

Review Codex CLI changelog updates against the user's Codex and dotfiles configuration, then recommend which new features are worth adopting. Use when the user mentions "codex 변경사항", "codex changelog", "codex 업데이트 검토", "codex release notes", "codex 버전", "최근…

write-genos-patch-notes

Create detailed Korean GenOS patch notes by reconciling a target release with its predecessor across curated release metadata, Git tags and diffs, migrations, configuration changes, and available Notion content, then save the note to the user's Obsidian vault…

Source text: Korean

obsidian-note

Use when user mentions "Obsidian", "옵시디언", "write as note", "save to notes", "노트로 저장", or /obsidian-note command. Do NOT use for TIL (use til), YouTube notes (use youtube-summarizer), GenOS 작업 지식 캡처 (use genos-knowledge-capture), GenOS 패치노트·릴리스 노트 (use…

Source text: Korean

cc-changelog-review

Review Claude Code CLI changelog updates against the user's dotfiles configuration and recommend which new features are worth adopting. Make sure to use this skill whenever the user mentions "claude code 변경사항", "체인지로그 검토", "claude code 업데이트 검토", "release…

api-design

Use when designing API endpoints, reviewing API contracts, adding pagination/filtering, or planning versioning strategy. Do NOT use for API consumption, client-side HTTP, or GraphQL.

Source text: Korean

java-modern-patterns

Use when writing Java 21+ code, refactoring to modern idioms, choosing records vs classes, using virtual threads, or applying pattern matching. Do NOT use for JPA (use jpa-patterns) or SQL optimization (use sql-optimization-patterns).

Source text: Mixed languages

jpa-patterns

Use when designing JPA entities, writing JPQL/Criteria queries, resolving N+1 problems, configuring HikariCP, or choosing ID generation strategies. Do NOT use for raw SQL optimization (use sql-optimization-patterns).

Source text: Mixed languages

python-patterns

Use when writing, reviewing, or refactoring Python code, designing data classes, implementing decorators, or choosing concurrency patterns. Do NOT use for linter/formatter config (use python-code-style) or testing (use python-testing).

Source text: Mixed languages

python-testing

Use when writing tests, setting up pytest, implementing TDD, creating fixtures, or mocking dependencies. Do NOT use for general patterns (use python-patterns) or style config (use python-code-style).

Source text: Korean

springboot-patterns

Use when building Spring Boot services, configuring profiles, implementing caching/async, setting up Actuator/Micrometer, or creating REST clients. Do NOT use for JPA (use jpa-patterns), API design (use api-design), security (use springboot-security), testing…

Source text: Korean

springboot-security

Use when configuring Spring Security, implementing JWT/OAuth2 auth, adding role-based access control, or hardening Spring Boot APIs. Do NOT use for general patterns (use springboot-patterns), JPA (use jpa-patterns), or testing (use springboot-tdd).

Source text: Korean

springboot-tdd

Use when writing tests, adding features TDD-style, or setting up test infrastructure for Spring Boot. Do NOT use for JPA/Testcontainers testing (use jpa-patterns), general TDD (use superpowers test-driven-development), or verification (use…

Source text: Korean

sql-optimization-patterns

Use when debugging slow queries, designing indexes, analyzing EXPLAIN output, resolving N+1 problems, or tuning database performance. Do NOT use for basic SQL, simple CRUD, or JPA entity design (use jpa-patterns).

Source text: Korean

find-docs

Use when looking up API references, library documentation, CLI commands, or checking version-specific behavior for any developer technology. Prefer this when documentation accuracy matters or model knowledge may be outdated. Do NOT use for general web search…

ast-grep

Guide for writing ast-grep rules to perform structural code search and analysis. Use when searching codebases by AST structure (negation, nesting, containment), finding specific language constructs, or running structural refactors beyond text search. Do NOT…

python-code-style

Use when configuring ruff/mypy/pyright, setting up formatting, writing docstrings, or establishing coding standards. Do NOT use for general patterns (use python-patterns) or testing (use python-testing).

Source text: Korean

git-commit-and-push

Use when user says "commit and push", "커밋하고 푸시", "올려줘", "저장하고 올려". Do NOT use for commit-only (use git-commit) or push-only (use git-push).

Source text: Korean

translate-article

Use when user provides a URL and asks to "translate", "번역", "한국어로", "Korean translation". Do NOT use for YouTube videos (use youtube-summarizer), original content (use tech-blog-writer), or Obsidian notes (use obsidian-note).

Source text: Korean

excalidraw-diagram

Create Excalidraw diagram JSON files that make visual arguments. Use when the user wants to visualize workflows, architectures, or concepts. Use when user says "다이어그램", "diagram", "excalidraw", "시각화", "아키텍처 그려". Do NOT use for Mermaid diagrams or draw.io.

genos-knowledge-capture

Use when GenOS 작업에서 얻은 재사용 가능한 지식(플랫폼 패턴·함정·고객사 결정)을 개인 Obsidian vault(Projects/GenonAI)에 기록할 가치가 생겼거나, GenOS 작업 맥락에서 사용자가 "지식 캡처", "vault에 정리/기록", "MOC", "읽는 순서", "field note", "/genos-knowledge-capture"를 요청할 때 사용. Do NOT use for: GenOS와 무관한 노트, 웹 리서치 기반 일반…

Source text: Korean

vault-linter

Use when user says "vault lint", "노트 점검", "vault 정리", "orphan notes", "링크 점검", or wants to check Obsidian vault health. Do NOT use for individual note creation (use obsidian-note) or tag management (use til-tagger).

Source text: Korean

agentic-notes

Use when the user asks to create an Obsidian note with an agent team, deep research, strict verification, multiple angles, or phrases like "팀으로 조사해서 노트", "깊게 조사해서 옵시디언 노트", "/agentic-notes", "--team", "--verify strict", or "--deep". Do NOT use for a simple…

Source text: Mixed languages

git-commit

Use when user wants to commit changes, says "commit", "커밋", "커밋해줘", "변경사항 저장". Do NOT use for pushing (use git-push) or commit-and-push (use git-commit-and-push).

Source text: Korean

tech-blog-writer

Use when user asks to write a blog post, tech article, tutorial, or "블로그 글 써줘". Do NOT use for TIL (use til), Obsidian notes (use obsidian-note), or code documentation.

Source text: Korean

til

Use when user mentions "TIL", "write TIL", "TIL 작성", "learning note", or /til command. Do NOT use for Obsidian notes (use obsidian-note) or blog posts (use tech-blog-writer).

Source text: Korean

adr

Use when making architectural decisions, choosing between frameworks/libraries/databases, deciding on data models, or recording any decision that would be expensive to reverse. Do NOT use for code documentation (comments belong in code), daily notes (use…

Source text: Korean

springboot-verification

Use before opening PRs, after major refactoring, or pre-deployment for Spring Boot verification. Do NOT use for writing tests (use springboot-tdd), security implementation (use springboot-security), or general patterns (use springboot-patterns).

Source text: Korean

youtube-summarizer

Use when user provides YouTube URL/link, mentions "youtube summarize", "유튜브 요약", "video summary", "transcript to note". Do NOT use for web article translation (use translate-article), regular Obsidian notes (use obsidian-note), or TIL (use til).

Source text: Korean

til-tagger

Use when user says "TIL 태그", "태그 업데이트", "tag TIL", "새 TIL 태그", or when Wiki has untagged files. Do NOT use for general Obsidian note tagging.

learning-tracker

Use when user says "learning summary", "what I learned today", "오늘 뭐 배웠지", "session summary", "학습 정리", or wants to extract learnings from current session. Do NOT use for session handoff (use session-handoff), development work logs (use devlog), or direct…

Source text: Korean

skill-guide

Use when user wants to create a new Skill, validate SKILL.md structure, or reference Anthropic skill design guide. Do NOT use for eval-based improvement or benchmark testing (use skill-creator plugin).

Source text: Korean

devlog

Use when user says "devlog", "작업 로그", "work log", "오늘 작업 기록". Supports /devlog, /devlog [title], /devlog --summary. Do NOT use for git commits (use git-commit), session handoff (use session-handoff), or TIL (use til).

Source text: Korean

git-push

Use when user says "push", "push to remote", "푸시해줘", or wants to send committed changes to remote. Do NOT use for commit creation (use git-commit) or commit-and-push (use git-commit-and-push).

github-actions

Use when user shares a GitHub Actions URL, mentions "CI failed", "빌드 실패", "workflow error", "Actions 실패", "파이프라인 실패", or wants to debug CI/CD issues. Do NOT use for creating workflow YAML, deploying, or non-GitHub CI.

Source text: Korean

project-overview

Use when user says "project analysis", "프로젝트 분석", "onboarding", "codebase overview", "project overview", "이 프로젝트 뭐야". Do NOT use for session handoff (use session-handoff), learning summaries (use learning-tracker), or debugging.

Source text: Korean

session-handoff

Generate comprehensive session summary for handoff to new LLM session. Use when user says "session handoff", "세션 인계", "세션 정리", "handoff", "다음 세션에 넘겨줘", or when ending a session and needing to preserve full context for continuation. Do NOT use for learning…

Source text: Korean

sns-writer

Use when user mentions tweet, thread, SNS post, "트윗", "스레드", or wants to polish social media writing. Do NOT use for blog posts (use tech-blog-writer), TIL (use til), or devlog (use devlog).

Source text: Korean