All authors
Claude Skills by m16khb-org
github.com/m16khb-org56 skills0 installs0 views
- Plans> **Summary**: 정보이론의 아버지 Claude Shannon의 개념(Signal-to-Noise Ratio, Entropy, Redundancy, Channel Capacity, Compression)을 코드 품질에 적용하는 **정량적 측정·게이트 스킬**을 설계한다. 기존 `ai-slop-clean`(정성적 휴리스틱)의 상호보완재로, PR 전 SNR 측정 → 목표 미달 시 개선 방향을 수치로 제시 → Turing Final Quality Gate에 통합. > **Deliverables**: Shannon 스킬(SKILL.md + references), SNR/Entropy/Redundancy 측정 프로토콜, Turing 품질 게이트 연동 > **Effort**: Medium > **Parallel**: YES — 2 waves > **Critical Path**: Task 1 → Task 2 → Task 5 → Final VerificationVotes: 0GitHub stars: 6
- Agent Usability LoopUse to improve how coding agents use a CLI, MCP server, or harness ("에이전트 사용성 개선", "agent QA 돌려줘", "autoresearch"): measures model-facing output, runs host agents in sandboxes, keeps or reverts one change per run.Votes: 0GitHub stars: 6
- Algorithm OptimizationUse when improving algorithmic performance, analyzing time or space complexity, choosing data structures, or verifying graph algorithms, dynamic programming, and correctness invariants.Votes: 0GitHub stars: 6
- Architecture ReviewUse when an architecture document, plan, or scope decision needs independent adversarial review before implementation, especially for excessive complexity or optimistic schedules. Run as an isolated sub-agent.Votes: 0GitHub stars: 6
- Aside Functional QaUse to verify through the Aside CLI that a browser feature, acceptance criterion, or user journey works as intended, with a reproducible evidence report (functional QA, regression check, 기능 QA, 요구사항 검증).Votes: 0GitHub stars: 6
- Aside Visual QaUse for UI/UX QA through the Aside CLI: design intent, accessibility, usability, responsive states, with an evidence-backed report (UI QA, UX review, 접근성 검토, 화면 QA, UI/UX 검수).Votes: 0GitHub stars: 6
- Aside Web QaUse for combined web QA through the Aside CLI, behavior plus UI/UX in one merged client report (통합 QA, 종합 QA, 웹 QA). Behavior only: aside-functional-qa; design/UX only: aside-visual-qa.Votes: 0GitHub stars: 6
- Atomic Commit PushUse to commit, split changes into atomic commits, or push a branch: narrow staging, Conventional Commit subject with a Lore body, no secrets. Rebase, bisect, conflicts, cherry-pick, worktrees: git-operations.Votes: 0GitHub stars: 6
- Code Quality MetricsUse when measuring code quality before and after cleanup, establishing quality baselines, detecting regressions across commits, or setting quantitative PR quality gates for signal, complexity, redundancy, and overhead.Votes: 0GitHub stars: 6
- Database Schema ArchitectureUse to design or review relational schemas: keys, normalization, partitioning, indexes, ORM entities and their SQL, slow queries, N+1, connection pools. IssueOps plan architecture review: architecture-review.Votes: 0GitHub stars: 6
- Diagram DesignMUST USE for any diagram or visual explanation (mermaid flowchart/sequence/state/ER, architecture sketch, gantt, chart, ASCII art): 다이어그램, 그림, 시각화, diagram, mermaid. Picks the best form and verifies it renders.Votes: 0GitHub stars: 6
- ExplainUse to explain concepts, code, plans, decisions, findings, or outcomes in the reader''s terms: "설명해줘", "쉽게 설명해줘", "어떤 근거야", "왜 이렇게 했어", "모르겠다", "explain how this works".Votes: 0GitHub stars: 6
- Fluent KoreanMUST USE whenever writing, revising, or reviewing Korean text or replying in Korean: clear, natural Korean that keeps code conventions and technical terms and removes AI-style patterns (AI티/slop).Votes: 0GitHub stars: 6
- Gates LedgerUse when a task needs a gate ledger ("게이트 원장", "gates 만들어줘", "수용 기준 체크"): turns acceptance criteria into G-numbered CHECK/EXPECT gates, fills EVIDENCE through `issueops gates`, abandons gates honestly.Votes: 0GitHub stars: 6
- Git OperationsUse when performing interactive rebase, bisect, conflict resolution, cherry-pick, history analysis, reflog recovery, or worktree management. Basic commit and push workflows belong to atomic-commit-push.Votes: 0GitHub stars: 6
- Gitlab UsecaseUse before GitLab, glab, or GitLab MCP work (IssueOps remote issue/MR, linked vs child items, issue-body updates, labels, assignee, target branch, Kody review threads, cleanup) to avoid repeated GitLab mistakes.Votes: 0GitHub stars: 6
- Implementation PlanningUse when the user asks for a plan, design, or architecture, or when work needs planning because it has five or more steps, ambiguous scope, multiple modules, or long-term architectural impact.Votes: 0GitHub stars: 6
- Io ModelUse to see or change the model and effort IssueOps uses per role (implement, review, research) for Claude Code or Codex, globally or per repo: io model, 역할별 모델 설정, 리뷰 모델 바꿔줘, 서브에이전트 모델.Votes: 0GitHub stars: 6
- Io UpdateUse for io update, issueops update, native skill refresh, or reinstalling the current IssueOps checkout: updates the binary and the Codex, Claude, Omo, omp, opencode integration without fetching source.Votes: 0GitHub stars: 6
- Issueops AbandonUse to pause or abandon an unmerged IssueOps cycle ("중단", "탈출", "일시 중단", "abandon the cycle"). Pause releases the lease; abandon closes PR/MR and issue and removes branch, worktree, record. Merged: issueops-cleanup.Votes: 0GitHub stars: 6
- Issueops CleanupUse after an IssueOps cycle merged, or for "이슈옵스 정리", "워크트리 지우고 브랜치 지우고 이슈 닫아줘": closes the linked issue and removes the worktree and local branch. Unmerged: issueops-abandon.Votes: 0GitHub stars: 6
- Issueops CompleteUse when a cycle in the pr phase has a published, verified draft PR/MR and an active lease, or for "완료 처리해줘", "사이클 끝내줘", "execution complete": records completion and releases the lease.Votes: 0GitHub stars: 6
- Issueops Create IssueUse at the start of an IssueOps cycle, when "issueops next" reports stage none or issue, or for "이슈 만들어줘", "이슈부터 시작하자", "child task 만들어줘". Records intent and publishes a readable Korean issue.Votes: 0GitHub stars: 6
- Issueops Create PrCreate and verify the linked GitHub PR or GitLab MR from an IssueOps execution lease, with a readable Korean body, branch and actor fencing, scored metadata, and safe recovery. Use in the PR/MR publication phase.Votes: 0GitHub stars: 6
- Issueops DebuggingUse when reproducing a bug, diagnosing a test failure, investigating a regression, or finding why a system is broken through systematic isolation and trace evidence.Votes: 0GitHub stars: 6
- Issueops DocsUse when `issueops next` reports docs, or for "문서 반영", "ADR 남겨줘", "주의사항 기록" in an IssueOps cycle: reflects the diff into the .issueops docs and records the project-docs-review verdict.Votes: 0GitHub stars: 6
- Issueops ImplementUse when "issueops next" reports implement.enter or implement, or for "구현 시작", "구현 이어서 해줘", "이슈 구현해줘", "child로 나눠서 구현해줘". Runs TDD in the canonical worktree under the lease.Votes: 0GitHub stars: 6
- Issueops MergeUse for "머지해줘", "PR 머지하고 정리", "merge the PR" on a completed IssueOps cycle: previews checks with `issueops remote merge-pr`, merges pinned to the completed head, deletes the remote branch, hands off to issueops-cleanup.Votes: 0GitHub stars: 6
- Issueops PlanPrepare the plan, reviews, and canonical worktree of an IssueOps cycle and hand off implementation. Use when `issueops next` reports plan.*, or for "아키텍처 정해줘", "계획 세워줘", "계획 검토해줘", "구현 인계".Votes: 0GitHub stars: 6
- Issueops PrepareGive an IssueOps cycle its branch identity: pin the base SHA, record `issueops branch prepare`, verify the provider branch link. Use for "준비", "브랜치 만들어줘", or when `issueops next` reports prepare.Votes: 0GitHub stars: 6
- Issueops Remote WriteUse before any governed "issueops remote ..." write (issue, child task, PR/MR body, comment, label, title, review reply) or for "원격에 써줘", "PR 본문 갱신". Renders, polishes, confirms, and reads back.Votes: 0GitHub stars: 6
- Issueops ReviewUse when issueops-plan or issueops-verify needs an independent review of a cycle architecture, plan, or implementation diff, or for "아키텍처 검토", "계획 검토", "구현 리뷰", "devil''s advocate" in an IssueOps cycle.Votes: 0GitHub stars: 6
- Issueops Slop CleanRun the IssueOps ai-slop-clean stage: remove agent residue from the task diff without changing behavior, re-verify, record evidence. Use when `issueops next` reports clean, or for "AI slop 정리", "정리 단계".Votes: 0GitHub stars: 6
- Issueops Sync IssueRefresh the body of an issue or provider-native child this cycle already published, with drift classification, managed-section preservation, and a body compare-and-swap. Use when a linked issue no longer matches its cycle.Votes: 0GitHub stars: 6
- Issueops Sync PrRefresh the body of a PR/MR this cycle already published, with generation and actor fencing, drift classification, and a fail-closed body compare-and-swap. Use when the diff moved on and the PR/MR description did not.Votes: 0GitHub stars: 6
- Issueops VerifyUse when "issueops next" reports the verify stage, or when the user asks to verify a sealed IssueOps implementation before publication.Votes: 0GitHub stars: 6
- IssueopsRoute an issue-driven work cycle to its current stage skill with `issueops next` and hold the invariants every stage shares. Use to start, resume, or continue an issue cycle: "이슈옵스", "이슈 작업 시작", "이어서 진행".Votes: 0GitHub stars: 6
- Meeting NotesUse to turn meeting transcripts, Clova Note exports, Slack huddle notes, or AI summaries into Korean minutes, Slack Canvas documents, action tables, Slack List entries, or reusable minutes prompts.Votes: 0GitHub stars: 6
- Pr ReviewUse to review or comment on a GitHub PR or GitLab MR by number, URL, or branch, including a second review after an automated reviewer. Replies to existing bot threads: review-agent-feedback. Not for uncommitted local diffs.Votes: 0GitHub stars: 6
- Project BootstrapUse to bootstrap a repository for issueops: AGENTS.md routing block, repo profile metadata, and the .issueops documents (via project-docs-bootstrap); later upkeep goes to project-docs-update and project-docs-optimize.Votes: 0GitHub stars: 6
- Project Docs BootstrapUse to create or regenerate a repository''s .issueops operating documents and AGENTS.md routing block from repository evidence. Incremental refresh: project-docs-update; restructuring: project-docs-optimize.Votes: 0GitHub stars: 6
- Project Docs OptimizeUse to split, reorganize, re-folder, or validate the `.issueops` document tree, or when its checker reports nested records, undeclared directories or root docs, broken links, or oversized documents.Votes: 0GitHub stars: 6
- Project Docs UpdateUse when a completed change, solved failure, new command, or durable decision should be reflected in existing .issueops docs outside an IssueOps docs stage. New docs: project-docs-bootstrap; restructuring: project-docs-optimize.Votes: 0GitHub stars: 6
- Prompt EngineeringUse when writing, testing, optimizing, or debugging LLM prompts, or converting vague requests into precise agent instructions with measurable output criteria.Votes: 0GitHub stars: 6
- Read Public ArtifactUse when a claude.ai/code/artifact link or other iframe-rendered page must be read and Artifact read/WebFetch fail (public-reader notice, SPA shell, Cloudflare 403): 아티팩트 읽어줘, 공유 아티팩트, public artifact.Votes: 0GitHub stars: 6
- Requirements AnalysisUse when analyzing Korean planning documents with Kordoc MCP to verify screenshots, small text, tables, OCR coverage, contradictions, omissions, and implementation requirements.Votes: 0GitHub stars: 6
- Review Agent FeedbackUse when a PR/MR has bot review threads (Kody, CodeRabbit, Copilot, Gemini) to verify against the code, reply, rate, and resolve: "봇 리뷰 검증해줘", "리뷰 스레드 resolve". New reviews: pr-review.Votes: 0GitHub stars: 6
- Self AugmentUse for self-augmentation, autonomous repo improvement, 95-point gate loops, or choosing the next valuable improvement: picks one change from repo evidence and GENIUS_THINK.md, implements it, verifies with self-verify.Votes: 0GitHub stars: 6
- Self VerifyRun or interpret the issueops self-verification loop: verify the harness, run the 95-point gate, inspect candidates, compare or promote baselines, confirm CLI/MCP/native integration health.Votes: 0GitHub stars: 6
- Sharing Backend WorkUse to write a Slack post sharing backend work (API or endpoint change, deploy, environment notice, investigation result, MR approval request, incident, report to the backend lead) with the dev team or backend peers.Votes: 0GitHub stars: 6