GitHub
neo4j-patterns
Neo4j driver best practices for Python. Use when working with Neo4j connections, Cypher queries, transactions, or GraphRAG implementations.
☆ 0View skill
Documentation AI Skills
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Categories: Documentation
Documentation Clear filters
Browse skills
GitHub
fastmcp-patterns
FastMCP server patterns for building MCP servers. Use when implementing MCP tools, resources, or server configuration.
☆ 0View skill
GitHub
ticket-feedback
レビュー指摘や発見した課題をLinearのタスクとして登録します
☆ 0View skill
GitHub
commit-push-pr-flow
タスク完了後に自動的に実行する必要があるフロースキルです
☆ 0View skill
GitHub
handle-ci-failure
CI (GitHub Actions) の失敗を検知・分析し、LinearのIssueとして登録します
☆ 0View skill
GitHub
process-commit
PRを作成する前に分割commitが必要な時に自動的に呼び出す必要があるスキルです
☆ 0View skill
GitHub
review-flow
PR作成後に自動的に実行する必要があるフロースキルです
☆ 0View skill
GitHub
process-ambiguous-task
指示の最初でコンテキストが不足している場合に自動的に呼び出す必要があるスキルです
☆ 0View skill
GitHub
worktree
Planが複雑/完了した直後に自動的に呼び出す必要があるスキルです
☆ 0View skill
GitHub
ralph-loop-pattern
Use this skill when implementing iterative development loops. This skill covers the Ralph-style continuous execution pattern, termination conditions, and progress tracking.
☆ 0View skill
GitHub
opencode-integration
Use this skill when integrating with OpenCode CLI for task execution. This skill covers CLI commands, session management, output parsing, and best practices for OpenCode integration.
☆ 0View skill
GitHub
fitness-evaluation-logic
Use this skill when evaluating system performance and determining if optimizations are successful. This skill covers fitness functions, metric collection, and improvement validation.
☆ 0View skill
GitHub
parallel-dispatch-logic
Use this skill when managing parallel execution of multiple tasks. This skill covers task queuing, concurrency control, state synchronization, and conflict resolution.
☆ 0View skill
GitHub
keiai-workflow
Use this skill when working with Keiai's 4-stage development workflow (Analysis, Planning, Solutioning, Implementation). This skill provides knowledge about the BMAD-METHOD inspired development process and how...
☆ 0View skill
GitHub
retrospective
Generate comprehensive learning documents by combining information from tickets, memories, GitHub PRs, and proposals. Use after completing significant work to capture lessons learned.
☆ 0View skill
GitHub
memory
Use for knowledge sharing across sessions. Search memory before starting work, store memory after learning. Critical for avoiding repeated mistakes and maintaining context.
☆ 0View skill
GitHub
memory-consolidation
Background process that proactively maintains memory hygiene. Scans for obsolescence to prune irrelevant data and synthesizes scattered information into higher-order patterns.
☆ 0View skill
GitHub
git-workflow
Use for any git operations: fixing PRs, creating commits, creating branches, pushing changes. Handles proper branch management, commit conventions, and stacked PRs.
☆ 0View skill
GitHub
ticket-management
Use when creating or updating tickets. Covers ticket writing best practices, what to include, and what to avoid.
☆ 0View skill
GitHub
proposal-execution
Use when executing approved proposals. Only memory_cleanup and test_gap proposals can be executed. Other types should use create_ticket_from_proposal directly.
☆ 0View skill
GitHub
proposal-reviewer
Acts as a Contextual Analyst. Reviews pending proposals by checking the codebase to establish *plausibility* and *value*. Approves proposals where the code context supports the suggested improvements.
☆ 0View skill
GitHub
orchestrator-workflow
Coordinates agent assignments and manages ticket lifecycle.
☆ 0View skill
GitHub
worker-workflow
Use for workflow guidance on HOW to work effectively. Covers task execution, decision escalation, and team coordination.
☆ 0View skill
GitHub
planning-code-folder-simplification
You are planning to simplify and improve a folder and its contents. The goal is to restructure the folder so that it is more understandable, maintainable and debuggable.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.