search-history
Search Claude conversation history from JSONL files. Use when looking for previous discussions, past decisions, code solutions, or context from earlier conversations.
Découvrez les skills DevOps, comparez leurs dépôts et consultez leurs instructions.
Search Claude conversation history from JSONL files. Use when looking for previous discussions, past decisions, code solutions, or context from earlier conversations.
Index markdown documentation - headings, diagrams, tables, code blocks, links. Use for quick overview without reading full files.
Quickly index and understand a codebase's architecture. Use at session start to get up to speed fast. Finds entry points, API routes, classes, models, configs, and patterns.
Find and understand project configuration files. Discovers build configs, dependencies, env vars, CI/CD, and tool settings without reading full files.
Dynamic agent composition and management system. USE WHEN user says create custom agents, spin up custom agents, specialized agents, OR asks for agent personalities, available traits, agent voices. Handles cust...
Use when executing implementation plans with independent tasks in the current session
Use when creating architecture diagrams, sequence diagrams, flowcharts, or any visual documentation from code analysis
Use when starting feature work, setting up fork, or creating isolated workspaces in NEO project
Use when creating new skills or editing existing skills in the .opencode configuration
Use when you have a written implementation plan to execute in a separate session with review checkpoints
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when you have a spec or requirements for a multi-step task, before touching code
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Takes the dual of a linear program (LP). Use when the user provides an LP in LaTeX or markdown and wants its dual, or asks about LP duality transformations.
リポジトリ構造定義書を作成するスキル
プロダクト要求定義書(PRD)を作成するスキル
機能設計書を作成するスキル
アーキテクチャ設計書を作成するスキル
プロジェクトの用語集を作成するスキル
コードレビューを実施し、品質監査レポートを生成するスキル
開発ガイドラインを作成するスキル
Diagnose and fix CI/CD failures related to Lint errors and test failures. Use when: (1) User mentions CI/CD failures, lint errors, or test failures, (2) User asks to fix code quality issues or make tests pass,...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.