Loading...
Loading...
Found 3,082 Skills
Issue creation expertise and convention enforcement. Auto-invokes when creating issues, writing issue descriptions, asking about issue best practices, or needing help with issue titles. Validates naming conventions, suggests labels, and ensures proper metadata.
Execute an implementation plan step-by-step with completion tracking. Use when the user wants to work through a plan, implement tasks sequentially, track progress on a task list, or asks to "execute the plan" or "start implementing".
Reproduce and investigate a bug using logs, console inspection, and browser screenshots
Check for and apply updates to installed skill branches from upstream.
Plan a new feature from concept to approved implementation plan. Activates Product Council for strategic evaluation, then Feature Council for technical planning. Produces a documented decision and scoped task breakdown. Use when starting any new feature work.
Audit PostHog survey SDK features and version requirements
Agent skill for swarm-issue - invoke with $agent-swarm-issue
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild/.NET build context. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ / .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build /bl:{}).
Primary pipeline review step after verified implementation. Use to create a PR with lineage and run architectural review before merge. Not for QA intake, planning, or implementation work.
This skill should be used when a designer is picking up a Task issue to add design coverage. Triggers on phrases like "I want to design task
Safely move all local worktree changes, including untracked files, onto a local target branch (default `develop`) using a worktree-aware stash/apply flow that preserves existing target-branch edits and surfaces conflicts for user direction.
Find branch coverage gaps in changed code and fix them by writing missing tests. Two analysis layers: Source ↔ Test (logic branches vs test cases) and Spec ↔ Test (requirement scenarios vs test cases, when a spec file is provided). Use when verifying test completeness after implementing a feature or fixing a bug, when auditing whether tests match a spec, or when suspecting untested branches.