Loading...
Loading...
Found 2,904 Skills
Commit Changes
Update the title and body of one or more pull requests.
Investigate and analyze the MistDuckCount/Bitdefender-Total-Security-Crack-2026 repository for security threats and malware distribution patterns
Analyze and understand malware distribution tactics, cracked software risks, and security threat detection patterns
WARNING - This repository distributes malware disguised as pirated Bitdefender antivirus software
Use this skill to triage a single newly opened, reopened, or `status/needs-triage`-labelled issue in microsoft/apm. Emit one synthesized comment with a triage decision, label set, milestone, and suggested next action.
Review pull requests for code quality, security issues, and best practices. Use when reviewing PRs, checking code changes, or analyzing diffs before merge.
Turn the working tree into logical, atomic Conventional Commits — classify uncommitted files as in-scope vs out-of-scope against the branch's merge base, show a staging plan, and create one commit per coherent unit (type + optional scope + British-English body; `!` / `BREAKING CHANGE:` for breaking changes). Never `git add -A`; files that look like they belong to another branch/worktree are never staged silently. Use when asked to commit uncommitted work, tidy WIP into atomic commits, or as the commit step inside a ship flow (e.g. `/send-it`). It commits only — no push, PR, changelog, or Linear writeback.
Use when performing a standalone PR double-check in a clean context — review, fix, and post.
Use when checking doc freshness and computing domain quality grades without making fixes.
Use when writing a mission report to the gateway DB from any operator mission.
Use when running the CTO flow-optimization loop — WIP scan, epic focus, triage unlabeled issues, and dispatch.