chann

@chann source repo

32 skills
0 followers
6 hours ago last updated

▌
Gcpr · chann bundle
Use only when the user explicitly invokes "/gcpr" or "$gcpr" as the short alias for "/git-commit-push-realtime" or "$git-commit-push-realtime". Delegates to that canonical skill without restating or weakening it. For a request phrased in natural language, use git-commit-push-realtime directly.

0
installs
▌
Bug Hunt · chann bundle
Use when something is broken, throwing, failing, flaky, or slower than it should be and the cause is not obvious, including "버그 원인 찾아줘", "이거 왜 안 되는지 추적해줘", "테스트가 간헐적으로 깨져", "성능이 갑자기 느려졌어", "diagnose this bug", "find the root cause", "this test is flaky", "/bug-hunt", or "$bug-hunt". Reproduces first, falsifies hypotheses in a written ledger, pins the fix with a check that failed for the defect's reason, and leaves a diagnosis record under `.bug-hunts/`. For defects found by reading a diff use code-review instead.

0
installs
▌
Gen Docs · chann bundle
Use when a software project needs README, README.ko, ARCHITECTURE, or USAGE documentation created, refreshed, reorganized, translated, or kept in sync without clobbering existing prose, including explicit "/gen-docs" or "$gen-docs"

0
installs
▌
Long Task · chann bundle
Use when the user asks to build a project end-to-end, run autonomous multi-hour or multi-day development, or orchestrate multi-milestone work without human intervention. Trigger phrases include "build this whole project", "implement this end-to-end", "do this autonomously", "run a long task", "long-running agent", "build it from scratch and don't ask", "/long-task", or "$long-task". Also use for lifecycle subcommands such as `/long-task status`, `/long-task pause`, `/long-task resume`, `/long-task clear`, and `/long-task complete`.

0
installs
▌
Review Me · chann bundle
Use only when the user explicitly invokes "/review-me" in Claude Code or "$review-me" in Codex to review a plan, design, or consequential decision one question at a time. Runs a read-only decision-tree interview and ends with a confirmed record in which every consequential branch is resolved, ruled out, or deliberately deferred. For defects in a Git diff use code-review instead.

0
installs
▌
Git Commit · chann bundle
Use when the user asks to commit changes, organize commits, write commit messages, or split working-tree changes into Conventional Commits. Trigger on phrases like "commit my changes", "커밋해줘", "커밋 분리", "make commits", "/git-commit", "$git-commit", or whenever the user wants to turn current changes into Conventional Commit-style commits. For commit + push use `git-commit-push`; for rewriting non-Conventional commit history use `git-commit-rewrite`.

0
installs
▌
Code Review · chann bundle
Use when the user asks to review code, review changes, review a commit, review a PR, audit code quality, check for security issues, or generate a code review report. Trigger on phrases like "review my changes", "코드 리뷰", "check my code", "review the last commit", "what do you think of this diff", "compare branches", "code audit", "HTML 리뷰 보고서", "styled review report", "/code-review", or "$code-review" — even if they don't say "code review" explicitly. Produces severity-tagged findings as a Markdown report plus a self-contained bilingual HTML report under `.reviews/`, opened in a browser. For a Markdown-only artifact use `code-review-md`.

0
installs
▌
Diff Viewer · chann bundle
Use when the user asks to render, inspect, open, or share the current git diff as a browser-readable HTML report, or explicitly invokes /diff-viewer, $diff-viewer, "diff viewer", "HTML diff", "split diff", or "unified diff".

0
installs
▌
Skill Audit · chann bundle
Use when packaged skills must be checked against the repository's skill contract before a merge or release, including "스킬 규칙 검사해줘", "스킬 패키지 점검", "스킬 카탈로그 동기화 확인", "audit my skills", "check every skill against the contract", "which skills are missing evals", "/skill-audit", or "$skill-audit". Reports every violation with its rule, file, and fix, and exits non-zero so it works as a gate. Read-only by default; use skill-forge to author or repair a package.

0
installs
▌
Skill Forge · chann bundle
Use when a skill package must be created, renamed, split, extended, or brought back into line with the repository's skill contract, including "스킬 새로 만들어줘", "스킬 패키지 만들어", "이 스킬 규칙에 맞게 고쳐줘", "add a new skill", "scaffold a skill package", "make this skill follow the contract", "/skill-forge", or "$skill-forge". Writes SKILL.md, the Codex descriptor, the slash command, evals, catalog and locale entries, published counts, and focused tests, then proves the result with skill-audit. Use skill-audit alone to inspect without changing anything.

0
installs
▌
Diff Summary · chann bundle
Use when the user wants an explanatory code, diff, branch, commit, or PR change summary, including "코드를 요약해줘", "변경사항을 요약해줘", "diff 요약", "main..dev 코드를 요약해줘", "브랜치 변경 요약", "PR 변경 요약", "summarize the code changes", "summarize this diff", "change summary", "main..dev summary", "what changed between branches", "summarize this PR", "/diff-summary", or "$diff-summary". Produces evidence-based purpose, behavior, architecture, patterns, contracts, tests, and operations in Markdown and interactive HTML. Use diff-summary-md for a Markdown-only artifact, diff-summary-quiz for a comprehension quiz, code-review for defects and risks, and diff-viewer for a raw patch; when both summary and review are requested, run distinct workflows.

0
installs
▌
Git Commit Push · chann bundle
Use when the user asks to commit working-tree changes AND push to the remote. Trigger on phrases like "commit and push", "커밋하고 푸시해줘", "/git-commit-push", "$git-commit-push", or "push my commits". Runs the git-commit workflow, then `git push` (never `--force`). For commit-only use `git-commit`; for history rewrite use `git-commit-rewrite`.

0
installs
▌
Plan Summary · chann bundle
Use when the user wants to summarize one or more explicit plans, PRDs, requirements, specifications, architecture proposals, implementation plans, or design documents, including "plan 요약", "PRD 요약", "설계문서 요약", "기획서 요약", "요구사항 문서 요약", "summarize this plan", "summarize this PRD", "design document summary", "architecture proposal summary", "/plan-summary", or "$plan-summary". Produces aligned Korean and English Markdown plus self-contained bilingual HTML. Use plan-summary-md for Markdown only and plan-summary-quiz for a comprehension quiz.

0
installs
▌
Work Summary · chann bundle
Use when the user wants coding-agent work history summarized or reported for today, yesterday, this or last week, month, quarter, or year, one date, or an explicit YYYY-MM-DD..YYYY-MM-DD span from local Claude Code, Codex, opencode, and agy session stores. Trigger on phrases like "오늘 작업 요약해줘", "이번 분기 작업 정리해줘", "올해 작업 상세 리포트", "what did I work on this quarter", "summarize my coding sessions", "/work-summary", or "$work-summary"; for one Git change use diff-summary instead.

0
installs
▌
Code Review Md · chann bundle
Use when the user asks for a Markdown-only code review artifact, a review file without HTML, or a review report in `.reviews/` with no browser output. Trigger on phrases like "review my changes and save as markdown", "마크다운 리뷰 보고서만", "리뷰 결과 마크다운 파일로 저장", "markdown-only review", "/code-review-md", or "$code-review-md". For the default markdown + HTML review use the `code-review` skill.

0
installs
▌
Git Merge To Dev · chann bundle
Use when the user asks to merge the current branch into the dev branch (`dev`, falling back to `develop`) and delete the merged source branch unless the source is protected. Trigger on phrases like "merge to dev", "dev에 머지", "develop에 합쳐줘", "merge this into dev and delete it", "/git-merge-to-dev", or "$git-merge-to-dev". For `main` use `git-merge-to-main`; to bulk-clean already-merged branches use `git-branch-cleanup`.

0
installs
▌
Diff Summary Md · chann bundle
Use when the user wants a Markdown-only diff or change summary artifact without an HTML report, including "요약을 마크다운 파일로만 저장해줘", "마크다운 요약만 저장", "마크다운 요약만 만들어줘", "diff 요약 마크다운으로", "markdown-only diff summary", "summarize the changes into a markdown file", "summary file without HTML", "/diff-summary-md", or "$diff-summary-md". For the interactive HTML report use diff-summary; for a summary with a comprehension quiz use diff-summary-quiz; for defects use code-review.

0
installs
▌
Git Merge To Main · chann bundle
Use when the user asks to merge the current branch into `main` and delete the merged source branch unless the source is protected. Trigger on phrases like "merge to main", "main에 머지", "main 브랜치에 합쳐줘", "merge this branch into main and delete it", "/git-merge-to-main", or "$git-merge-to-main". Refuses to force-delete or to operate on a dirty working tree. For `dev` use `git-merge-to-dev`; to bulk-clean already-merged branches use `git-branch-cleanup`.

0
installs
▌
Gen Backend Handoff · chann bundle
Use when code changes, API changes, database changes, jobs, queues, auth behavior, git diffs, commit ranges, branch comparisons, or current session context need to be turned into a handoff for backend developers, platform engineers, or server-side coding agents, including explicit "/gen-backend-handoff" or "$gen-backend-handoff"

0
installs
▌
Gen Session Handoff · chann bundle
Use when the current session must be handed to a fresh agent or another person because context is running out, the work spans sessions, or someone else will continue it, including "지금까지 작업 인수인계 문서로 만들어줘", "다음 세션에서 이어갈 수 있게 정리해줘", "컨텍스트 정리해서 넘겨줘", "hand this session off", "write a handoff so a new agent can continue", "summarize where we are so I can resume tomorrow", "/gen-session-handoff", or "$gen-session-handoff". Separates proven state from unproven, names the exact command behind each proven claim, and ends with a copyable resume prompt. For handing API changes to client or server developers use gen-frontend-handoff or gen-backend-handoff.

0
installs
▌
Git Branch Cleanup · chann bundle
Use when the user asks to clean up, prune, or delete local branches that have already been merged. Trigger on phrases like "clean up local branches", "merged 브랜치 정리", "이미 머지된 브랜치 삭제", "prune merged branches", "/git-branch-cleanup", or "$git-branch-cleanup". Deletes local branches whose tip is reachable from at least one protected branch (`main`, `master`, `dev`, `develop`, `development`, `stg`, `stage`, `staging`, `root`), excluding the protected list and the current branch. Uses `git branch -d` (safe delete) only — never `-D`.

0
installs
▌
Git Commit Rewrite · chann bundle
Use when the user asks to rewrite recent non-Conventional commit subjects, fix existing commit messages, or clean up commit history. Trigger on phrases like "rewrite commit history", "fix these commit messages", "커밋 메시지 다시 써줘", "/git-commit-rewrite", "$git-commit-rewrite", or whenever the user shows a non-Conventional `git log` and asks for help. For new commits use `git-commit`; for commit + push use `git-commit-push`.

0
installs
▌
Gen Frontend Handoff · chann bundle
Use when backend API changes, server behavior changes, git diffs, commit ranges, branch comparisons, or current session context need to be turned into a handoff for frontend, mobile, SDK, or other client developers and coding agents, including explicit "/gen-frontend-handoff" or "$gen-frontend-handoff"

0
installs
▌
Plan Summary Md · chann bundle
Use when the user wants an explicit plan, PRD, requirements, specification, or design document summarized into Korean and English Markdown files only, including "plan 요약을 마크다운으로", "PRD 요약 파일", "설계문서 마크다운 요약", "markdown-only plan summary", "summarize this PRD as Markdown", "/plan-summary-md", or "$plan-summary-md". For bilingual HTML use plan-summary; for a quiz use plan-summary-quiz.

0
installs
▌
Diff Summary Quiz · chann bundle
Use when the user wants a change summary plus a self-test quiz about a diff, branch, commit, or PR, including "diff 퀴즈 만들어줘", "변경사항 퀴즈", "요약하고 퀴즈로 확인해줘", "이 변경 이해했는지 퀴즈로 확인", "quiz me on this diff", "diff summary with quiz", "test my understanding of this change", "/diff-summary-quiz", or "$diff-summary-quiz". For a summary without a quiz use diff-summary; for a Markdown-only artifact use diff-summary-md; for defects use code-review.

0
installs
▌
Git Commit Realtime · chann bundle
Use when the user wants an implementation committed continuously at meaningful checkpoints while pushing stays a separate, explicit step. Trigger on phrases like "commit as you work", "keep committing without pushing", "작업 중간중간 커밋만", "푸시 없이 의미 단위마다 커밋", "/git-commit-realtime", "$git-commit-realtime", or the short aliases "/gcr" and "$gcr". Runs verified, outcome-based Conventional Commit checkpoints and keeps every checkpoint local.

0
installs
▌
Research Brief · chann bundle
Use when a technical question must be answered from primary sources and the answer needs to survive being quoted later, including "이거 공식 문서에서 확인해줘", "어떤 방식이 맞는지 근거까지 찾아줘", "라이브러리 동작 조사해줘", "research how this API behaves", "find out whether X supports Y", "check the spec on this", "/research-brief", or "$research-brief". Produces a cited brief under `.research/` with a bottom-line answer, a claim table naming each source's tier and verified version, a contradiction ledger, and mandatory open questions. For summarizing a document you already have use plan-summary instead.

0
installs
▌
Plan Summary Quiz · chann bundle
Use when the user wants an explicit plan, PRD, requirements, specification, or design summary plus a comprehension quiz, including "plan 요약 퀴즈", "PRD 이해도 퀴즈", "설계문서 요약하고 퀴즈", "quiz me on this plan", "PRD summary quiz", "/plan-summary-quiz", or "$plan-summary-quiz". For a summary without a quiz use plan-summary; for Markdown only use plan-summary-md.

0
installs
▌
Build Reinstall · chann bundle
Use when the user explicitly invokes "/build-reinstall" or "$build-reinstall", or explicitly asks to build and reinstall a local app or CLI after finishing development work, including "빌드하고 다시 설치해줘", "새로 빌드해서 설치까지", or "rebuild and reinstall the CLI". Builds with project-owned commands, reinstalls only a proven build, and verifies that the installed copy matches it. Never start it on its own as a post-completion step.

0
installs
▌
Git Resolve Conflicts · chann bundle
Use when a merge, rebase, cherry-pick, revert, or stash pop has stopped with conflicts and the working tree must be finished rather than abandoned, including "충돌 해결해줘", "머지 컨플릭트 정리해줘", "rebase 중에 멈췄어", "resolve these conflicts", "finish this merge", "fix the conflict markers", "/git-resolve-conflicts", or "$git-resolve-conflicts". Classifies every conflicted path, recovers both sides' intent before touching a hunk, records which intent survived, and runs the project's own checks. Never aborts and never invents behavior. For merging a clean branch use git-merge-to-main or git-merge-to-dev.

0
installs
▌
Git Commit Push Realtime · chann bundle
Use when the user wants an implementation committed and pushed continuously at meaningful checkpoints instead of only once at the end. Trigger on phrases like "commit and push as you work", "keep committing and pushing", "작업 중간중간 커밋 푸시", "의미 있는 단위마다 푸시", "/git-commit-push-realtime", "$git-commit-push-realtime", or the short aliases "/gcpr" and "$gcpr". Runs verified, outcome-based Conventional Commit checkpoints and pushes each one immediately without force.

0
installs
▌
Human Friendly Writing · chann bundle
Use when AI-written Korean text needs to read like a person wrote it — it contains AI-flavored jargon such as 계약(contract), 엔벨로프(envelope), 패리티(parity), leaked framework vocabulary like "열린 노드가 없습니다", or translation-ese rhythm. Trigger on "AI 용어 없애줘", "사람답게 다듬어줘", "AI 슬롭 제거", "자연스러운 한국어로 윤문해줘", "/human-friendly-writing", or "$human-friendly-writing". Korean text only; not a spell-checker, not a translator, never changes content.

0
installs

32 published skills