Git & VCS
Git operations, commit helpers, branch management
discover-cicd
by rand
Automatically discover CI/CD and automation skills when working with GitHub Actions, Jenkins, GitLab CI, pipelines, continuous integration, continuous deployment, or automated testing. Activates for CI/CD development tasks.
history-analyzer
by lis186
Analyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.
history
by lis186
Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors
tinybird-cli-guidelines
by tinybirdco
Tinybird CLI commands, workflows, and operations. Use when running tb commands, managing local development, deploying, or working with data operations.
local-issue
by DoiiarX
"本地文件系统 issue 管理。Use when the user wants to create, update, or close a local issue, report a bug, add a feature request, or track a task in the local file-based issue system. Triggers on: local issue, 本地issue, 创建issue, 新建issue, bug report, feature request, 关闭issue, 创建任务."
uni-helper
by uni-helper
Comprehensive skill reference for uni-helper ecosystem - AI-powered development tools for uni-app
frappe-state-machine-helper
by Venkateshvenki404224
Generate state machine logic for Frappe DocTypes. Use when implementing complex status workflows, state transitions, or document lifecycle management.
frappe-data-migration-generator
by Venkateshvenki404224
Generate data migration scripts for Frappe. Use when migrating data from legacy systems, transforming data structures, or importing large datasets.
python-clean-code
by ertugrul-dmr
Use when writing, fixing, editing, reviewing, or refactoring any Python code. Enforces Robert Martin's complete Clean Code catalog—naming, functions, comments, DRY, and boundary conditions.
explain-like
by ArjenSchwarz
Explain code changes or designs at three expertise levels (beginner, intermediate 5-10 yrs, expert). Use for: (1) PR/branch change explanations - understand what changed and why, (2) Design document validation - self-review by explaining at multiple levels to catch gaps or logic issues. Triggers: "explain this PR", "explain these changes", "validate this design", "explain like I'm a beginner", "walk me through this at different levels".
roasbeef-prose
by Roasbeef
Writing style guide for Roasbeef's technical prose. This skill should be used when writing PR descriptions, commit messages, technical documentation, blog posts, or any written content that should match Roasbeef's established voice. Activate when creating PRs, drafting commit messages, writing release notes, or composing technical explanations.
commit
by ArjenSchwarz
Commits
permission-analyzer
by ArjenSchwarz
Generate Claude Code permissions config from session history. Use when setting up autonomous mode, configuring .claude/settings.json, avoiding --dangerously-skip-permissions, or analyzing what permissions a project needs. Reads session logs to extract Bash commands and MCP tools actually used, then generates appropriate allow/deny rules.
catchup
by ArjenSchwarz
Catch Up on Branch Changes
starwave:creating-spec
by ArjenSchwarz
Initialize a new spec with requirements, design, and task planning. Orchestrates the entire spec-driven workflow from feature idea to actionable task list.
fix-bug
by ArjenSchwarz
Systematic bug investigation, resolution, and documentation. Use when fixing bugs that need thorough analysis, test coverage, and a formal bugfix report. Applies systematic debugging methodology, creates regression tests, and generates a standardized report in specs/bugfixes/<bug-name>/. Triggers on requests like "fix this bug", "debug and document this issue", or when a bug needs both resolution and documentation.
been-there-done-that
by rfxlamia
Guides an agent to document developer progress objectively after completing a sprint, project phase, or milestone. Reads a global markdown file, detects git work sessions via 3-day gap analysis, writes factual entries (no sycophancy, no praise), and performs cross-entry progression analysis for portfolio and gig use. USE WHEN: User says "document my progress", "log what I did", "I just finished [sprint/project/phase]", "update btdt", or provides a repo path after completing work. WORKFLOW: Pre-flight → Session Detection → Collection → Analysis → Write → Confirm OUTPUT: Extends the user's global progress log (been-there-done-that.md) with a dated, factual entry placed at the correct position in a Year/Month/Date/Project tree. Default output language: English (ask user on first run if file is new). CRITICAL: Agent MUST stop and wait at every STOP gate. Do not proceed without explicit user confirmation. No assumptions. No skipping.
tinkering
by rfxlamia
Safe experimentation framework for AI agents. Creates isolated sandbox environments for trying new features, testing approaches, and exploring solutions without polluting the main codebase. USE WHEN: Agent needs to try something uncertain, explore multiple approaches, test a new library, prototype a feature, or run a technical spike before committing to implementation. PRIMARY TRIGGERS: "experiment with" = Setup sandbox + run experiment "try this approach" = Quick experiment in sandbox "spike" / "POC" / "prototype" = Time-boxed technical investigation "tinker" / "tinkering mode" = Enter experimentation workflow "explore options" = Multi-approach comparison in sandbox NOT FOR: Debugging (use debugger), testing (use test runner), or committed feature work (use git branches). DIFFERENTIATOR: Unlike git branches (for committed direction), tinkering is for "I don't know if this will work" exploration. Try 5 things in sandbox before committing to a branch. Faster feedback, zero codebase pollution.
baby-education
by rfxlamia
Makes agent explain concepts with extreme clarity for beginners learning new topics or projects. Uses analogies-first approach, visual mental models, and ELI5 style to transform complex technical explanations into accessible learning experiences. Trigger when user is new to a technology, starting a project, or explicitly requests simple explanations.
git-precommit
by u9401066
提交前編排器 + Paper-Aware Pre-Commit Hooks。 LOAD THIS SKILL WHEN: commit、提交、推送、做完了、收工 CAPABILITIES: 記憶同步、文檔更新、Paper 品質把關、Git 操作
gitnexus-cli
by docxology
"Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\""
nix
by i9wa4
Nix commands and package management guide. Use when: - Running nix build, nix run - Adding custom packages - Using nurl for hash acquisition
github
by i9wa4
GitHub operations guide using gh CLI. Use when: - Working with GitHub Issues - Managing sub-issues (parent-child relationships) - Posting comments to a PR - Posting inline comments to a PR - Replying to PR comments - Checking diffs with line numbers
git
by i9wa4
Git operations guide. Provides how-to for common git tasks. Use when: - Writing commit messages (Conventional Commits format) - Understanding git workflows