القائمة
Check typos in the current project (English and Korean). Scans variables, functions, comments, docs, and strings. Run before commits or on demand. Use when user asks to check spelling, find typos, or review text quality.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create or edit Jira issues on boards the user has access to. Use this skill whenever the user asks to create, add, file, open, write, or edit a Jira issue/ticket/task, mentions `/jira-create-issue`, `jira 이슈 생성`, `지라 이슈 만들어`, `이슈 수정`, or asks to "티켓 올려줘", even when the project or issue key is not stated explicitly — the skill will infer the project from conversation context or present accessible boards for the user to pick. Always trigger this over generic jira lookup when the intent is to create or modify an issue.
Review changes, run lint/format, then create a git commit with English message. Use when user wants to commit, save changes, or says "커밋", "git commit", "git ci".
Explain programming language syntax in Korean with concise examples. Use when user asks about syntax like "python list comprehension", "go goroutine", "rust ownership", or any programming concept explanation.
Review GitHub PRs and track improvements as tasks. Use when user asks to review a PR, check a pull request, says "PR 리뷰해줘", "PR 봐줘", or provides a GitHub PR URL or number. Delegates both the review judgment and comment writing to the `reviewer` agent (run in the background).
Run language-specific linters, formatters, and static type checks with full command reference. Use when user asks to lint, format, type-check, check style, or says "린트", "포맷", "타입 체크", "lint", "format", "type check", "biome", "ruff", "pyright", "clippy", "golangci-lint", "rumdl", "prettier", "shfmt". Also use when needing detailed command variants (check-only, fix-only, partial scope) beyond the standard fix-everything command.
Create GitHub issues with auto-generated English titles and contextual body content. Use when the user wants to create an issue, report a bug, request a feature, file a ticket, or says "이슈 만들어줘", "이슈 생성", "버그 리포트", "feature request". Also trigger when the user discusses a bug or feature and then says "이거 이슈로 올려줘" or similar.
| name | typos |
| description | Check typos in the current project (English and Korean). Scans variables, functions, comments, docs, and strings. Run before commits or on demand. Use when user asks to check spelling, find typos, or review text quality. |
| allowed-tools | Agent(typo-checker), Bash(typos:*), Bash(git diff:*), Bash(git status:*), Bash(fd:*), Bash(rg:*), Bash(printf:*) |
| model | sonnet |
| effort | low |
프로젝트의 오타, 철자 오류, 네이밍 불일치를 검사한다.
Input: $ARGUMENTS
/typos src/, /typos README.md)git status로 변경된 파일을 우선 검사한다인자를 파싱하여 검사 대상을 결정한다
인자가 없으면 git status로 변경된 파일을 확인한다
typo-checker 에이전트를 실행하여 대상 파일의 오타를 검사한다
결과를 파일 경로와 함께 정리하여 보고한다:
printf에 ANSI 녹색(\033[32m ... \033[0m) escape 코드를 씌워 터미널에 녹색으로 출력한다:printf '\033[32m%s\033[0m\n' "$(cat <<'EOF'
오타 리포트
...
EOF
)"