Sponsored by

Find leads on Reddit on auto pilot

Topic: vscode

98 skills in this topic.

referee Final arbiter for Bug Hunter. Receives Hunter findings and Skeptic challenges, independently re-reads code, and delivers authoritative verdicts with CVSS scoring and proof-of-concept generation for security findings.
codexstar69/bug-hunter 114
security-review Run a focused STRIDE-based security review using Bug Hunter-native artifacts. Use whenever the user asks for a full security audit, repository security review, weekly security scan, PR security review with deeper validation, or wants dependency CVEs and threat-model context combined into one workflow.
codexstar69/bug-hunter 114
skeptic Adversarial code reviewer for Bug Hunter. Rigorously challenges each reported bug to determine if it's real or a false positive. Uses doc-lookup (Context Hub + Context7) to verify framework claims before disproval. The immune system that kills false positives.
codexstar69/bug-hunter 114
threat-model-generation Generate or refresh a STRIDE-based threat model for the current repository using Bug Hunter-native artifacts. Use whenever the repository has no threat model yet, the architecture changed materially, a security review needs fresh trust-boundary context, or the user explicitly asks for a threat model.
codexstar69/bug-hunter 114
vulnerability-validation Validate security findings for exploitability, reachability, and real-world impact using Bug Hunter-native findings artifacts. Use after security scans, before patch generation, or whenever the user wants confirmation that a suspected vulnerability is actually exploitable.
codexstar69/bug-hunter 114
commit-security-scan Scan code changes for security vulnerabilities using Bug Hunter-native artifacts and STRIDE context. Use whenever the user asks for PR security review, commit-diff scanning, staged-change security checks, branch-comparison security review, or pre-merge security analysis of changed code.
codexstar69/bug-hunter 114
prompt-architect Analyzes and improves prompts using 27 research-backed frameworks across 7 intent categories. Use when a user wants to improve, rewrite, structure, or engineer a prompt — including requests like "help me write a better prompt", "improve this prompt", "what framework should I use", "make this prompt more effective", or any prompt engineering task. Recommends the right framework based on intent (create, transform, reason, critique, recover, clarify, agentic), asks targeted questions, and delivers a structured, high-quality result.
ckelsoe/prompt-architect 100
pull-requests Guide for creating, updating, and following up on pull requests in the Coder repository. Use when asked to open a PR, update a PR, rewrite a PR description, or follow up on CI/check failures.
coder/coder 12,860
refine-plan Iteratively refine development plans using TDD methodology. Ensures plans are clear, actionable, and include red-green-refactor cycles with proper test coverage.
coder/coder 12,860
code-review Reviews code changes for bugs, security issues, and quality problems
coder/coder 12,860
doc-check Checks if code changes require documentation updates
coder/coder 12,860
deep-review Multi-reviewer code review. Spawns domain-specific reviewers in parallel, cross-checks findings, posts a single structured GitHub review.
coder/coder 12,860
skill-creator Guide for creating effective skills. This skill 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.
Tiberriver256/mcp-server-azure-devops 357
azure-devops-rest-api Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the vsts-rest-api-specs repository.
Tiberriver256/mcp-server-azure-devops 357
release-note-writer Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code.
microsoft/vscode-docs 6,457
release-note-reviewer Review VS Code release notes for style, structure, and completeness. Use for reviewing Insiders or Stable release notes against writing guidelines. Produces an actionable list of recommendations.
microsoft/vscode-docs 6,457
frontmatter-description Check and optimize MetaDescription frontmatter fields in VS Code documentation. Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles.
microsoft/vscode-docs 6,457
docs-product-alignment Audit and update docs/copilot/ documentation to accurately reflect current VS Code AI capabilities. Use when: competitive analysis reveals gaps, product launches new features, docs use outdated framing, or keyword coverage needs strengthening for discoverability by users and AI agents. Produces a gap analysis plus targeted edits across affected files.
microsoft/vscode-docs 6,457
content-redirect Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
microsoft/vscode-docs 6,457
add-icon Add new icons to the GitLens GL Icons font
gitkraken/vscode-gitlens 9,774
add-test Generate unit or E2E test files for existing code
gitkraken/vscode-gitlens 9,774
add-command Create new VS Code commands with all required boilerplate
gitkraken/vscode-gitlens 9,774
deep-review Use when reviewing a change set before merge, when tracing code paths for correctness, or when a thorough merge-blocking review is needed rather than a surface-level checklist
gitkraken/vscode-gitlens 9,774
deep-planning Use when formulating the best technical approach for a task — before writing implementation plans or code. Triggers on architecture decisions, complex features, refactors, or when the user asks how to approach something. Investigates current codebase, questions existing patterns, researches alternatives, and presents approaches with trade-offs.
gitkraken/vscode-gitlens 9,774