- Skills
- 325
- 仓库
- 1
- 职业覆盖
- 7
- 场景覆盖
- 6
- Stars
- ★ 0
ImaginerLabs 的 Skills 325
setup-test-data
Master test data setup: creating meaningful test fixtures, test data factories, and managing test data lifecycle. Use when user needs test data, test fixtures, sample data for tests, or when tests are hard to maintain due to data setup. Triggers especially when user says "test fixtures", "test data", "setup test", "create test objects", or "sample data".
security-review
AI-powered codebase security scanner that reasons about code like a security researcher — tracing data flows, understanding component interactions, and catching vulnerabilities that pattern-matching tools miss. Use this skill when asked to scan code for security vulnerabilities, find bugs, check for SQL injection, XSS, command injection, exposed API keys, hardcoded secrets, insecure dependencies, access control issues, or any request like "is my code secure?", "review for security issues", "audit this codebase", or "check for vulnerabilities". Covers injection flaws, authentication and access control bugs, secrets exposure, weak cryptography, insecure dependencies, and business logic issues across JavaScript, TypeScript, Python, Java, PHP, Go, Ruby, and Rust.
safe-refactor
Chain-combined skill that ensures refactoring is done safely by combining refactor judgment, test coverage verification, and pre-commit review. Encapsulates the decision of WHEN to refactor, HOW to ensure safety, and WHAT verification is needed. Use when user mentions refactoring, code restructuring, improving code quality, or when they want to refactor without breaking behavior. Triggers especially when user says "should I refactor this?", "is it safe to refactor?", "how do I refactor without breaking things?", or "refactor my code".
reproduce-bug
Master reliable bug reproduction: how to construct minimal reproduction cases, isolate conditions, and verify bugs consistently. Use when debugging, creating bug reports, or when a bug is hard to reproduce. Triggers especially when user says "reproduce bug", "can't reproduce", "minimal case", "bug report", or "isolating the bug".
refactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
read-test-coverage
Master reading test coverage reports: how to interpret coverage metrics, understand what they mean, and identify untested gaps. Use when analyzing code coverage, identifying test gaps, or when coverage numbers don't match expectations. Triggers especially when user says "test coverage", "coverage report", "interpret coverage", "untested code", or "what's not tested".
react-performance
Reviews and optimizes React component performance and correctness. Covers stale closures, unnecessary re-renders, useEffect cleanup, state design, debounce/throttle, and race conditions. Should be used when the user is concerned about React performance — slow renders, stale closure bugs, or optimizing useMemo/useCallback usage. Distinguished from frontend-code-review which covers general code quality, this skill focuses specifically on React performance and Hook-related issues.
react-component-refactor
Analyzes React component structure, identifies reusable units, and refactors large or messy components into clean, well-organized code. Strictly maintains 1:1 logic equivalence — only structure changes, never behavior. Should be used when the user wants to refactor a React component — splitting a monolith, reorganizing a messy file, or restructuring for better maintainability. Distinguished from react-component-extraction which extracts specific reusable pieces, this skill restructures the entire component.
react-component-extraction
Extracts reusable UI or stateful logic into independent components or custom Hooks. Analyzes context dependencies, evaluates extraction boundaries, and ensures zero breakage for existing callers. Should be used when the user wants to extract, split, or isolate a piece of React code — creating reusable components, custom Hooks, or separating concerns within a large component. Distinguished from react-component-refactor which restructures the entire component, this skill focuses on extracting specific reusable pieces.
pre-commit-review
Chain-combined skill that merges git-commit behavior with code-review judgment to create intelligent pre-commit workflow. Encapsulates the decision of WHEN to require review before commit, WHAT to check in pre-commit review, and HOW to structure commit workflow. Use when user mentions pre-commit review, commit with review, pre-commit checks, or when they want to establish commit quality gates. Triggers especially when user says "should I review before commit?", "what should I check before committing?", "commit workflow", or when they're unsure whether their commit is ready.
intelligent-test-creation
Chain-combined skill for creating comprehensive, intelligent tests by combining test-think (what to test), generate-mock (mocking strategy), and setup-test-data (test fixtures). Use when user needs to write tests, wants intelligent test coverage, or when they're unsure what tests to write for a feature. Triggers especially when user says "write tests for this", "how to test this", "test coverage", "what tests do I need", or "generate test cases".
inspect-state
Master runtime state inspection: how to examine variable values, object state, and data structures during execution. Use when debugging, understanding variable contents, or when code behavior is unexpected. Triggers especially when user says "inspect variable", "check state", "what's in this object", "variable value", "runtime inspection" or "debug state".
git-stash-management
Master git stash: when to stash, how to organize stashes, naming strategies, and recovery patterns. Use when user mentions git stash, stashing changes, saving work in progress, or when they have uncommitted changes they need to set aside. Triggers especially when user says "should I stash this?", "git stash", "save my changes", "switch branches with uncommitted work", or "recover stash".
git-rebase-safety
Master safe rebasing: when to use rebase vs merge, how to handle conflicts, and how to ensure history integrity. Use when user mentions rebasing, git rebase, rebase conflicts, rebase vs merge, or when they're unsure about rebasing strategy. Triggers especially when user says "should I rebase?", "rebase vs merge", "how to resolve rebase conflicts", or "is it safe to rebase?".
git-merge-resolution
Master git merge conflict resolution: when to merge vs rebase, conflict handling strategies, and maintaining clean merge history. Use when user encounters merge conflicts, git merge issues, or when they need to combine branch histories. Triggers especially when user says "merge conflict", "resolve conflicts", "git merge", "merge strategy", or "conflicts in git".
git-history-rewrite
Master git history manipulation: when modifying history is safe, git reset/rebase alternatives, and maintaining history integrity. Use when user mentions git history, rewriting commits, git reset, amending commits, or when they want to clean up commit history. Triggers especially when user says "clean up history", "rewrite git history", "git reset", "amend commit", or "squash commits".
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
git-branch-strategy
Master Git branching decisions: when to create branches, naming conventions, branch lifecycle management, and cleanup strategies. Use when user mentions branching, branch names, git workflow, branch management, or when they're unsure about which branch to create or how to organize branches. Triggers especially when user says "should I create a branch?", "what should I name this branch?", "branch naming convention", "how to organize branches", or "when to create a branch".