코딩 규칙, 프레임워크, 리팩터링, 코드 리뷰 (1.5만건)
Set up and use ReMe as a file-native long-term memory system through the reme CLI. Use when an Agent needs to detect whether ReMe is installed or running, install and configure ReMe, start or verify its local service, retrieve prior context, or write and consolidate durable memory.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a contribution schedule and calculate a supplied price-path cost basis without predicting returns. Use when the user asks to dollar-cost averaging with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Separate reported claims from impact inferences, with related assets and next checkpoints. Use when the user asks to news impact with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Volatility Snapshot via the published AlphaGBM interface. Use for this focused function, not as a promise that every website API accepts API keys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Aggregate user-supplied disclosed buys and sells by source without automatically copying trades. Use when the user asks to smart money tracking with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Score observed price trend, confirmation, risk and participation without forecasting a price. Use when the user asks to momentum following with AlphaGBM. Use the bundled Python runner; never silently replace real results with demos.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stock Analysis via the published AlphaGBM interface. Use for this focused function, not as a promise that every website API accepts API keys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Options Score via the published AlphaGBM interface. Use for this focused function, not as a promise that every website API accepts API keys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds the backend of an app clone: auth, database migrations and access rules, payments with Stripe, email, background jobs and third-party integrations through official APIs only, plus a security checklist. Use when the user says "add login", "set up auth", "wire up the database", "add payments", "connect Stripe", "add Google Calendar", "send emails", "backend for my clone", or when /replica-build is running on fake data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Use for architecture orientation, impact analysis, what-would-break questions, or finding callers. Uses CodeGraph when available and a dependency-free builtin fallback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Browse or compare wiki knowledge by originating AI tool. Use for cross-tool memory questions, tool-specific knowledge, or gap/diff analysis between Codex, Claude, Hermes, and other agents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, callback not continuing, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose a named CCB agent by combining authoritative runtime and job lineage with deep read-only pane inspection, apply bounded recovery when evidence supports it, verify the result, and request authorization before submitting a redacted GitHub issue. Use for `$ccb_diagnose agentname`, `$ccb-diagnose agentname`, or reports that a CCB agent is stuck, disconnected, not continuing, not replying, or showing provider errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enable or disable tmux-bound disconnect recovery for the current Codex thread. Use only for the explicit invocations `$reconnect on` or `$reconnect off` inside a Codex CLI running in tmux.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recover CCB agents, panes, mounts, provider contexts, API/provider failures, config reload aftermath, clear operations, and guarded single-agent restarts. Use when the user asks to fix, recover, restart if safe, clear context, reload, remount, or keep work going after provider/API failure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a reply did not arrive, or what to check first.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enable or disable tmux-bound disconnect recovery for the current Codex thread. Use only for the explicit invocations `$reconnect on` or `$reconnect off` inside a CCB-managed or ordinary tmux Codex CLI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Idiomatic context.Context usage in Golang — propagation through API boundaries, cancellation, timeouts and deadlines, request-scoped values, context.WithoutCancel for background work outliving requests. Apply when designing context propagation across layers, debugging leaked or unexpired contexts, choosing between context.Background/TODO/WithoutCancel, or storing values in context. Not for code that merely accepts ctx as first parameter.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for structural refactors, extracting functions, or moving code between packages (→ See `samber/cc-skills-golang@golang-refactoring` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.