Loading...
Loading...
Found 10,137 Skills
Conduct targeted code exploration on a repository, and document the process of "Asking Questions → Reading Code → Reaching Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific problem and provide conclusions), module-overview (organize the structure, boundaries, entry points, and dependencies of a module), spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: When users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". For the distinction from learning / tricks / decisions, refer to the root skill `easysdd`.
Propose a change with optional working artifacts. Use when the user wants a structured proposal with design notes, tasks, and a clear path to implementation.
Analyses git changed files in the workspace and makes atomic, functional, and semantic commits using conventional commits format. Use when the user asks to commit changes, create commits from staged/unstaged files, or organise working tree changes into meaningful commits.
Kadoa integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Kadoa data.
Break down a requirement that is "too large to be implemented as a single feature" into a list of sub-features with dependencies and statuses, and place it in the independent `codestable/roadmap/{slug}/` directory — serving as the seed and scheduling basis for subsequent multiple feature processes. Two modes: new (draft a new roadmap from a large requirement), update (refresh an existing roadmap: add items, modify dependencies, reorder, mark as drop). Division of labor with requirements / architecture — those two record "what the system is now", while the roadmap records "what we plan to do next". Trigger scenarios: Users say "I want an X system", "Help me break down this requirement", "Schedule this large requirement", "Create a roadmap", or it is found during the feature-design phase that the requirement is too large to fit into a single feature.
Follow this sub-process when fixing bugs — turn the verbal description of "problem found" into a closed loop from verification to repair, leaving three documents: problem report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code" to avoid common pitfalls: the problem description in your mind disappears after the fix, you only fix the surface without analyzing the root cause, the scope of repair expands and cannot be traced, and you don't know if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing artifacts. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only retaining the fix-note.
Holistic, system-aware planning before implementing non-trivial tasks. Use when the task involves new features, architectural decisions, multi-file changes, unclear requirements, or multiple valid approaches. Triggers on "/plan", "plan this", "design an approach", "let's plan first".
Pancake CRM integration. Manage Recordses. Use when the user wants to interact with Pancake CRM data.
피치 스킬 사용 중 발견된 문제점/노하우를 구조화하여 docs/스킬피드백/에 문서화하는 범용 스킬. "스킬 개선", "피드백 정리", "문제점 기록", "스킬 리뷰", "개선사항", "스킬 피드백" 키워드로 트리거. 모든 피치 스킬에 범용 적용 가능. 다른 AI 에이전트가 문서를 읽고 스킬을 개선할 수 있도록 구성.
Chatsonic integration. Manage Users, Chats, Images, Workspaces, Prompts. Use when the user wants to interact with Chatsonic data.
Persistent project-scoped store for deep research on large topics. Use for substantive questions - comparing libraries, evaluating tools, surveying solutions to hard problems. Not for plan notes, not for small facts, not for code-level decisions, not for ideas.
Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.