All categories
Development
Programming, frameworks, implementation, frontend, backend, and app development
- 77,303
- 3,221
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse development skills
Showing 22,945–22,968 of 77,303 skills
- Scaffold FeaturePlan and implement a full-stack featureVotes: 0GitHub stars: 124
- ReleaseVersion bump, changelog, tag, push release, and mark the Sentry issues it fixesVotes: 0GitHub stars: 124
- Release ProtocolVersion bump, changelog, tag, and push a @kangentic/protocol release, independent of the Kangentic desktop releaseVotes: 0GitHub stars: 124
- Pull RequestCreate a PR and drive its CI checks to all-green (auto-fixing code and de-flaking/rewriting tests), then stop. Never merges. This is the Testing column skill. Use /merge-pull-request to merge a green PR.Votes: 0GitHub stars: 124
- PreviewOpen dev server for previewing live code changesVotes: 0GitHub stars: 125
- Merge Pull RequestMerge an already-green PR (rebase merge, delete branch) and fast-forward the local main checkout for HMR. This is the Merge column skill. It assumes the Testing column (/pull-request) already drove the PR to green. Not for creating a PR (use /pull-request) or a direct quick-push (use /merge-back).Votes: 0GitHub stars: 124
- Merge BackDirect quick-push escape hatch - commit, rebase, and push straight to the source branch, bypassing the PR gate. Use only when the user explicitly asks to push, land, or merge back a quick change. The normal flow is the board (Testing -> /pull-request, Merge -> /merge-pull-request). NOT for a plain local commit (use /commit for that).Votes: 0GitHub stars: 124
- Ipc BridgeIPC bridge checklist for adding or modifying endpoints across all 7 layersVotes: 0GitHub stars: 124
- Debug ActivityDiagnose activity-engine issues - a task shows active or idle wrongly, the board indicator is stuck, false thinking or false idle, activity engine debugging playbookVotes: 0GitHub stars: 125
- Cross PlatformCross-platform pitfalls for shell handling, paths, and file operationsVotes: 0GitHub stars: 124
- CommitCreate a LOCAL commit only - stage and commit on the current branch with no push and no rebase. Use for "commit" / "commit changes" / "commit current changes" / "save my work". NOT for pushing, landing, or merging back (use /pull-request or /merge-back for that).Votes: 0GitHub stars: 124
- Code ReviewReview git changes for quality and conventions via parallel reviewer subagents synthesized in the main agent (auto-fixes findings, fills red-green test-coverage holes, and commits that pass locally by default)Votes: 0GitHub stars: 124
- Add MigrationAdd a new database migrationVotes: 0GitHub stars: 124
- Add Ipc EndpointScaffold a new IPC endpoint across all 7 layersVotes: 0GitHub stars: 124
- TourInteractive onboarding walkthrough for a new engineer. Use for "give me a tour", "onboard me", "walk me through the codebase".Votes: 0GitHub stars: 40
- Testing StrategyDesign test strategies and test plans with coverage targets. Complements /draft:coverage which measures what this skill plans. Auto-loaded by /draft:implement before TDD.Votes: 0GitHub stars: 40
- Tech DebtIdentify, categorize, and prioritize technical debt across seven dimensions. Generates remediation plans with effort estimates. Offered by /draft:new-track for refactor tracks.Votes: 0GitHub stars: 40
- ReviewCanonical review parent command. Runs the default three-stage review for tracks or project changes, and routes to quick-review, bughunt, deep-review, or assist-review when the user asks for explicit review depth or when the review context justifies escalation.Votes: 0GitHub stars: 40
- Quick ReviewAd-hoc PR/diff/file review. No track context needed. Four dimensions — security, performance, correctness, maintainability. Use for one-off reviews when you don't have or don't need a Draft track.Votes: 0GitHub stars: 40
- PlanPrimary router for planning, architecture, and track management workflows. Analyzes user intent and dispatches to new-track, decompose, adr, tech-debt, change (and related). Use for starting features, breaking down work, recording decisions, managing debt, or handling scope changes.Votes: 0GitHub stars: 40
- New TrackStart a new feature or bug track. Collaborative intake process with structured questions, AI guidance, and progressive refinement before generating spec.md and plan.md. Use when the user asks to 'start a new track', 'create a feature track', 'add a bug fix track', or says 'I want to build X', 'fix the Y bug', 'plan a refactor'.Votes: 0GitHub stars: 40
- LearnScan codebase to discover coding patterns and update draft/guardrails.md. Learns conventions (skip in future) and anti-patterns (always flag). Supports migration from workflow.md and pattern promotion.Votes: 0GitHub stars: 40
- InitInitialize Draft project context for Context-Driven Development — the single, scope-aware entry point (works at the repo root or inside any sub-module; no separate index command). Builds the root-first code-graph knowledge memory (draft/graph/, with a module→root link) and creates product.md, tech-stack.md, workflow.md, tracks.md, architecture.md (brownfield), .ai-context.md (derived), and .ai-profile.md. Supports --graph-only (graph memory only, no markdown) and --module-only. Use when the u...Votes: 0GitHub stars: 40
- Incident ResponseIncident management lifecycle — triage, communicate, mitigate, postmortem. Three modes — new (start incident), update (status update), postmortem (blameless RCA report).Votes: 0GitHub stars: 40