
Claude Skills by NeoLabHQ
github.com/NeoLabHQGuide for setup arXiv paper search MCP server using Docker MCP
Guide for setup Codemap CLI for intelligent codebase visualization and navigation
Guide for setup Context7 MCP server to load documentation for specific technologies.
Guide for setup Serena MCP server for semantic code retrieval and editing capabilities
Display the current state of the FPF knowledge base
Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
Use after writing tests to assess coverage quality across structural, mutation, requirements, and API/integration dimensions; organized knowledge for choosing and interpreting coverage analyses.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testing
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
Use when tackling complex reasoning tasks requiring step-by-step logic, multi-step arithmetic, commonsense reasoning, symbolic manipulation, or problems where simple prompting fails - provides comprehensive guide to Chain-of-Thought and related prompting techniques (Zero-shot CoT, Self-Consistency, Tree of Thoughts, Least-to-Most, ReAct, PAL, Reflexion) with templates, decision matrices, and research-backed patterns
This skill should be used when need prioritize what changed code in repository human must review.
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation
Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals
Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
Add missing test coverage for your local code changes by generating new test files (covers uncommitted and untracked changes, or the latest commit if everything is committed). Use when you want write tests for new logic or increase test coverage.
Guide for creating effective skills using a TDD-based approach. This command treats skill creation as Test-Driven Development applied to process documentation. - Purpose - Create reusable skills that extend Claude's capabilities - Output - Complete skill directory with SKILL.md and optional resources ```bash /create-skill ["skill name"] ```
Verify skills work under pressure and resist rationalization using the RED-GREEN-REFACTOR cycle. Critical for discipline-enforcing skills. - Purpose - Test skill effectiveness with pressure scenarios - Output - Verification report with rationalization table ```bash /test-skill ["skill path or name"] ```
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context engineering choices, or measuring improvement quality.
Comprehensive guide for skill development based on Anthropic's official best practices - use for complex skills requiring detailed structure
Understand the components, mechanics, and constraints of context in agent systems. Use when writing, editing, or optimizing commands, skills, or sub-agents prompts.
Comprehensive guide for creating Claude Code agents with proper structure, triggering conditions, system prompts, and validation - combines official Anthropic best practices with proven patterns
Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration
Create and configure git hooks with intelligent project analysis, suggestions, and automated testing
Use when found gap or repetative issue, that produced by you or implemenataion agent. Esentially use it each time when you say "You absolutly right, I should have done it differently." -> need create rule for this issue so it not appears again.
Guide for creating effective skills. This command should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
Create a workflow command that orchestrates multi-step execution through sub-agents with file-based task prompts
Use this skill when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testing
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
Use when tackling complex reasoning tasks requiring step-by-step logic, multi-step arithmetic, commonsense reasoning, symbolic manipulation, or problems where simple prompting fails - provides comprehensive guide to Chain-of-Thought and related prompting techniques (Zero-shot CoT, Self-Consistency, Tree of Thoughts, Least-to-Most, ReAct, PAL, Reflexion) with templates, decision matrices, and research-backed patterns
Update and maintain project documentation for local code changes using multi-agent workflow with tech-writer agents. Covers docs/, READMEs, JSDoc, and API documentation.
Apply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
Reconcile the project's FPF state with recent repository changes
Manage evidence freshness by identifying stale decisions and providing governance actions
Execute complete FPF cycle from hypothesis generation to decision
Search the FPF knowledge base and display hypothesis details with assurance information
Reset the FPF reasoning cycle to start fresh
Display the current state of the FPF knowledge base
Analyze a GitHub issue and create a detailed technical specification
Add line-specific review comments to pull requests using GitHub CLI API
Create well-formatted commits with conventional commit messages and emoji
Create pull requests using GitHub CLI with proper templates and formatting
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.
Use when working on multiple branches simultaneously, context switching without stashing, reviewing PRs while developing, testing in isolation, or comparing implementations across branches - provides git worktree commands and workflow patterns for parallel development with multiple working directories.
Load all open issues from GitHub and save them as markdown files
Use to load open/unresolved PR review comments then aggregate them as tasks in .specs/comments/*.md for parallel agents to fix.
Verify what PR review comments have been addressed (committed/pushed OR uncommitted local changes) and resolve the threads that are genuinely fixed or no longer relevant.
Comprehensive A3 one-page problem analysis with root cause and action plan