Loading...
Loading...
Found 2,776 Skills
Identify and report potentially malicious software repositories masquerading as legitimate security tools
Use when extracting BDD specs from existing code — for adopting Beat in an established codebase or distilling a module into feature files
WARNING - This repository appears to be malware distribution disguised as legitimate software cracks
Analyze and understand malware distribution tactics, cracked software risks, and security threat detection patterns
Archive completed changes and merge specification differences into permanent documents. Used when changes have been deployed, are ready for archiving, or when specifications need to be updated after implementation. Trigger words include "openspec archive", "archive", "archive proposal", "merge specifications", "complete proposal", "update documents", "finalize specifications", "mark as completed".
This skill should be used when the user says "get PR comments", "show PR feedback", "what comments on my PR", "PR review comments", "show me the review", "what did reviewers say", or asks about feedback on a pull request. Not for creating PRs or responding to comments.
This skill should be used when the user says "commit my changes", "commit this", "create a commit", "git commit", "save my work", or mentions committing code.
Triage and orchestrate code reviews. Analyzes PR intent, identifies touched surfaces, assesses risk, and routes to specialist skills. Does NOT perform detailed review - delegates to specialists. Supports full pipeline with "Review PR <number>" command.
Spawn a focused code review subagent. Use after every RED/GREEN cycle (pass the files changed in that cycle), after a commit, or whenever the user asks for a review. Always use this skill for reviews — it ensures the review lens is test-first and findings are fix-oriented.
Use when preparing a pull request for merge: inspect diffs, collect checks and review comments, classify findings, fix safe issues, verify, and loop until merge-ready.
Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.
Skill for handling PR code reviews. Use when triggered by a PR review comment, review request, or when asked to review code changes. Provides workflow for reading review comments, understanding feedback, and iterating on changes.