khaledsaeed18/dotclaude
39 skills
$npx skills add khaledsaeed18/dotclaudeSkillInstalls
accessibility-auditAudit UI code or a running page against WCAG 2.2 AA, covering semantics, keyboard access, focus management, labels, contrast, ARIA misuse, and motion,…adversarial-reviewerReview code through three hostile personas - the Saboteur, the New Hire, and the Security Auditor - each required to find at least one issue.api-design-reviewReview an API contract (REST or GraphQL) before or while it is implemented, checking resource naming, HTTP semantics, status codes, error shape, pagination,…brainstormingTurn a rough idea into a fully formed, written design through collaborative dialogue — exploring intent, requirements, and trade-offs one question at a time,…changelogGenerate a changelog or release notes from Git history, grouped by change type, written in user-facing language, with issue/PR links and breaking changes…code-review-responseProcess code-review feedback with technical rigour — understand each point, check it against the actual codebase, and respond with reasoning or implementation…create-agentAuthor a new subagent for this repository end to end by scaffolding it with pnpm new, curating its tool allowlist, setting model, color, and memory in…create-commandAuthor a new slash command for this repository end to end by scaffolding it with pnpm new, writing the frontmatter and argument handling, drafting the prompt…create-hookAuthor a new Claude Code hook for this repository end to end by scaffolding it with pnpm new, writing the hook script and its settings.json wiring, documenting…create-skillAuthor a new skill for this repository end to end by choosing its category, writing trigger-friendly frontmatter, structuring the SKILL.md, splitting reference…db-migration-safetyReview or write a database schema migration with production safety as the bar, checking lock behavior, table rewrites, backfill strategy, deploy-order…dependency-auditAudit a project's dependencies for outdated and vulnerable packages and surface breaking-change notes for upgrades.executing-plansExecute a written implementation plan task by task, reviewing it critically first, following each step exactly, running every verification, and stopping to ask…explain-codebaseOnboard to an unfamiliar codebase by mapping its architecture, entry points, and data flow.finish-branchWrap up a completed development branch by verifying tests pass, detecting the workspace state, then presenting clear merge / PR / keep / discard options and…fix-ciDiagnose and fix a failing CI run by pulling the actual failure logs (gh run view --log-failed), reproducing the failure locally, fixing the root cause rather…git-commitCommit work the right way by gathering full repo state, respecting the project's commitlint/pre-commit/branch rules, staging only understood files, and writing…git-undoRecover safely from Git mistakes such as discard, unstage, amend, reset, revert, restore lost commits via reflog, recover deleted branches, and fix bad…git-worktreesSet up an isolated workspace for feature work so the current branch and working tree stay untouched — detecting existing isolation first, preferring the…gitignoreGenerate or repair a .gitignore tailored to the project's actual stacks, frameworks, OS, and editors, and untrack files that are already committed but should…grill-meRelentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved.grill-with-docsStress-test a plan against the project's existing domain model by challenging terminology, surfacing contradictions with code, and updating CONTEXT.md and ADRs…handoffCompact the current conversation into a handoff document for another agent to pick up.improveissue-writerTurn a rough bug report, idea, or complaint into a well-formed, actionable issue - investigating the codebase first to add reproduction steps, expected vs…merge-conflictResolve Git merge, rebase, cherry-pick, revert, and stash conflicts safely by understanding both sides and the operation in progress before integrating, then…owasp-securityReview code being written or modified against the OWASP Top 10:2025 and ASVS secure-coding requirements, catching vulnerability classes before they ship.parallel-agentsFan independent work out to multiple subagents that run concurrently, each with a focused scope and self-contained instructions, then review and integrate…performance-optimizationOptimize a performance problem by profiling to find the real bottleneck before changing anything, making one targeted change, and verifying both the…pr-descriptionGenerate a clear, reviewer-friendly pull-request description from a diff, covering what changed, why, risk, and how it was tested.release-tagCut a release by determining the SemVer bump from history, updating version files across any stack, refreshing the changelog, creating an annotated (optionally…secret-scanScan code or a diff for hardcoded secrets (API keys, tokens, passwords, private keys, and other exposed credentials) before they get committed or shipped.solid-principlesApply the SOLID principles as design diagnostics when writing, reviewing, or refactoring code with classes, modules, or service boundaries - detecting god…standup-summaryGenerate a standup or weekly-review update from actual work evidence - commits, branches, PRs, and issues across one or more repositories - grouped into done /…systematic-debuggingDebug a bug, test failure, crash, or unexpected behaviour by finding the root cause before changing anything, instead of guessing at fixes.test-driven-developmentImplement a feature or bugfix test-first using the red-green-refactor cycle — write a failing test, watch it fail, write the minimal code to pass, then clean…verify-completionGate every "it works / it's fixed / tests pass / done" claim behind fresh evidence — run the actual verifying command, read its output, and only then state the…webapp-testingVerify a web application works correctly in a real browser using Playwright.writing-plansTurn a spec or set of requirements into a detailed, task-by-task implementation plan an engineer (or a subagent) can execute without further context.