Loading...
Loading...
Found 6,189 Skills
Realm integration. Manage data, records, and automate workflows. Use when the user wants to interact with Realm data.
DB 스키마 추출 스킬. DB의 현재 상태를 테이블별 DDL 파일로 추출하여 schema/ 폴더에 저장. "스키마 추출", "스키마 업데이트", "extract-schema", "DB 스키마 동기화", "스키마 파일 갱신", "DB 구조 확인", "DDL 추출", "스키마 최신화" 키워드로 트리거. 스키마 파일과 실제 DB 상태가 다를 수 있다고 판단되면 이 스킬을 사용하라.
Actian integration. Manage data, records, and automate workflows. Use when the user wants to interact with Actian data.
Git Worktrees enables parallel development by maintaining multiple checked-out branches simultaneously in separate directories.
Document finalized technology selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent documents. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four types: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively push when important choices are made after feature-design or issue-analyze, or when the user says "record decision", "archive technology selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive under-discussion solutions.
Conduct a targeted code exploration of the repository, and document the process of "Ask Questions → Read Code → Draw Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific question and provide conclusions), module-overview (sort out the structure, boundaries, entry points, and dependencies of a module), and spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: Users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / tricks / decisions.
Onboard a new repository or a repository with scattered documents into the CodeStable system. Two paths are automatically determined: the empty repository path (no spec-type documents or codestable/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial codestable/ structure) first generates an audit report + migration mapping plan, which is finalized after user confirmation one by one. This skill only does two things: "build the skeleton" and "organize existing documents". Once the skeleton is built, all sub-workflows can run directly. Trigger scenarios: Users say "Use CodeStable in this project", "Build CodeStable structure", "Initialize CodeStable", "Migrate to CodeStable".
Use this before claiming work is complete, fixed, or tested—before committing or creating a PR—you must run validation commands and confirm the output before claiming success; always back up assertions with evidence
Performs a comprehensive health check of a CockroachDB cluster. Gathers deployment context first, then provides tier-appropriate diagnostics. Self-Hosted uses SQL against node-level system tables and CLI. Advanced/BYOC use Cloud Console and SQL with node visibility. Standard monitors provisioned compute and workload via Cloud Console. Basic monitors Request Unit consumption and connectivity. Use for daily checks, pre-maintenance validation, post-incident verification, or production readiness assessment.
Analyzes CockroachDB range distribution across tables and indexes using SHOW RANGES to identify range count, size patterns, leaseholder placement, and replication health. Use when investigating hotspots, uneven data distribution, range fragmentation, or validating zone configuration effects without DB Console access.
Validate pending migrations for foreign key consistency, rollback safety, and best practices
ClickHouse integration. Manage data, records, and automate workflows. Use when the user wants to interact with ClickHouse data.