convez.ai
SkillAutomaçãoIntermediário
KhaledSaeed18

dotclaude

KhaledSaeed18/dotclaude

Extensões reutilizáveis para Claude Code: skills, agents, commands e hooks

Ver no GitHub
BomPluginScore · de 0 a 100

Coleção de extensões reutilizáveis para Claude Code: 31 skills, 7 agents, 5 commands e 5 hooks. Instala diretamente no seu projeto sob `.claude/` via registry shadcn, permitindo automação de tarefas repetitivas e delegação inteligente de trabalhos especializados.

Instalação

$npx convez-ai KhaledSaeed18/dotclaude

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
5
Forks
0
Acompanhando
0
Saúde
85%
Último commit
há 2 dias
Versão
—
Issues abertas
4
Contribuidores
2

Casos de uso

  • Automatizar tarefas repetitivas em desenvolvimento (commits, análise de segurança)
  • Delegar pesquisa, code review e tarefas focadas a agents especializados
  • Acionar ações específicas via commands personalizados no fluxo de trabalho
  • Executar scripts automaticamente em eventos do Claude Code (hooks)

Veredito

Conjunto bem estruturado e prático de extensões para Claude Code. Excelente para quem quer potencializar fluxos de desenvolvimento automatizando padrões recorrentes, com clara separação entre skills (automáticas), agents (delegadas), commands (manuais) e hooks (reativas).

README

A tradução para o português deste README ainda está na fila.

My personal collection of Claude Code extensions, distributed as a shadcn GitHub registry.

Items install into the current project under .claude/, so run the install command from your project root. (shadcn writes into the project you run it in; its ~ means "project root", not your home directory, so a skill lands in <project>/.claude/skills/<name>/.)

Skills, agents, commands, and hooks

If you are new to Claude Code extensions, here is what each kind is and when you would reach for it. They differ mainly in who or what sets them off.

  • Skill. A reusable procedure Claude loads on its own when your request matches what the skill is for. You do not have to ask for it by name. Reach for a skill when you keep repeating the same multi-step task and want Claude to just know how to do it well (for example, writing a good commit or scanning for leaked secrets).
  • Agent. A specialist Claude can hand a whole side task to, working in its own separate context and handing back just the result. Reach for an agent when a job would otherwise flood the main conversation with noise, like deep web research or a focused code review.
  • Command. A shortcut you trigger yourself by typing /name. Reach for a command when you want to kick something off deliberately, on your timing, rather than leaving it to Claude to decide.
  • Hook. A script that runs automatically on an event in Claude Code, such as before a tool runs or when a session ends. Reach for a hook when you want something to happen every single time, with no model judgment involved, like logging or a safety check.

The table under What installs where shows where each one lands on disk and what triggers it.

Install

Install any item with the shadcn CLI:

npx shadcn@latest add KhaledSaeed18/dotclaude/<item>

For example, run this from your project root and the handoff skill lands in .claude/skills/handoff/:

npx shadcn@latest add KhaledSaeed18/dotclaude/handoff

What installs where

Each item installs under .claude/, by type:

TypeInstalls toTriggered by
Skills.claude/skills/<name>/Claude, automatically, when the description matches the task
Agents.claude/agents/<name>.mdClaude delegating to the subagent, or you invoking it
Commands.claude/commands/<name>.mdYou, by typing /<name>
Hooks.claude/hooks/<name>/A settings.json event you wire up (see below)

Hooks need one extra step. shadcn copies the hook's script and its HOOK.md, but it can't edit your settings.json. After installing a hook, open its HOOK.md and add the documented block to .claude/settings.json to activate it.

Want an item available globally (in every project)? Install it into a project as above and copy it into your home config — folders for skills and hooks, single files for agents and commands:

cp -R .claude/skills/handoff ~/.claude/skills/        # skills & hooks: folders
cp .claude/agents/code-reviewer.md ~/.claude/agents/  # agents & commands: single files

Skills and hooks that bundle companion files install them in the same folder, and the cp -R above carries them across automatically.

Catalog

The catalog below lists every item in this repository, grouped by type and then category.

Skills

Engineering

SkillDescriptionInstall
adversarial-reviewerReview code through three hostile personas - the Saboteur, the New Hire, and the Security Auditor - each required to find at least one issue. Use when a standard review feels too comfortable, when code is going into a critical path, when a previous review missed bugs that later surfaced, or when you want coverage across correctness, clarity, and security in a single pass.npx shadcn@latest add KhaledSaeed18/dotclaude/adversarial-reviewer
code-review-responseProcess code-review feedback with technical rigour — understand each point, check it against the actual codebase, and respond with reasoning or implementation rather than reflexive agreement. Use when you receive review comments (from a human, the code-reviewer agent, or any reviewer) and are about to act on them, especially if any feedback seems unclear or wrong.npx shadcn@latest add KhaledSaeed18/dotclaude/code-review-response
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 frontmatter, then writing a focused system prompt and regenerating the registry. Use when creating, scaffolding, or reviewing an agent or subagent in this repo.npx shadcn@latest add KhaledSaeed18/dotclaude/create-agent
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 body, then regenerating the registry. Use when creating, scaffolding, or reviewing a slash command in this repo.npx shadcn@latest add KhaledSaeed18/dotclaude/create-command
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 activation in HOOK.md, then regenerating the registry. Use when creating, scaffolding, or reviewing a hook in this repo.npx shadcn@latest add KhaledSaeed18/dotclaude/create-hook
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 material into companion files, then regenerating the registry and README catalog. Use when creating, scaffolding, restructuring, or reviewing a skill in this repo.npx shadcn@latest add KhaledSaeed18/dotclaude/create-skill
executing-plansExecute a written implementation plan task by task, reviewing it critically first, following each step exactly, running every verification, and stopping to ask rather than guessing when blocked. Use when you have a plan document (such as one from the writing-plans skill) and need to implement it in this session.npx shadcn@latest add KhaledSaeed18/dotclaude/executing-plans
explain-codebaseOnboard to an unfamiliar codebase by mapping its architecture, entry points, and data flow. Use when starting work in a new or unknown repository and you need a navigable mental model fast.npx shadcn@latest add KhaledSaeed18/dotclaude/explain-codebase
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 inline as decisions crystallise.npx shadcn@latest add KhaledSaeed18/dotclaude/grill-with-docs
parallel-agentsFan independent work out to multiple subagents that run concurrently, each with a focused scope and self-contained instructions, then review and integrate their results. Use when you face two or more genuinely independent tasks — separate failing test files, unrelated bugs, distinct subsystems — that share no state and don't depend on each other's order.npx shadcn@latest add KhaledSaeed18/dotclaude/parallel-agents
performance-optimizationOptimize a performance problem by profiling to find the real bottleneck before changing anything, making one targeted change, and verifying both the improvement and that correctness did not degrade. Use when a feature is measurably slow, a page load or API response exceeds a budget, a query is taking too long, or a user reports sluggishness. Do not use to pre-optimize code that has not been measured to be slow.npx shadcn@latest add KhaledSaeed18/dotclaude/performance-optimization
systematic-debuggingDebug a bug, test failure, crash, or unexpected behaviour by finding the root cause before changing anything, instead of guessing at fixes. Works in any language or stack. Use when something is broken, a test is failing, behaviour is wrong, or a previous fix didn't hold.npx shadcn@latest add KhaledSaeed18/dotclaude/systematic-debugging
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 up. Works in any language or test runner. Use when building new behaviour or fixing a bug and you want the test to actually prove the code works.npx shadcn@latest add KhaledSaeed18/dotclaude/test-driven-development
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 result. Use before committing, opening a PR, marking a task complete, handing off to or trusting a subagent, or otherwise asserting that work succeeded.npx shadcn@latest add KhaledSaeed18/dotclaude/verify-completion
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. Breaks work into bite-sized steps with exact file paths, real code, and verification commands. Use before starting a multi-step build, once you know what you're building.npx shadcn@latest add KhaledSaeed18/dotclaude/writing-plans

Productivity

SkillDescriptionInstall
brainstormingTurn a rough idea into a fully formed, written design through collaborative dialogue — exploring intent, requirements, and trade-offs one question at a time, then proposing approaches and capturing the agreed design in a spec before any code is written. Use at the start of any creative or feature work, when the idea isn't yet concrete enough to plan or build.npx shadcn@latest add KhaledSaeed18/dotclaude/brainstorming
grill-meRelentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved.npx shadcn@latest add KhaledSaeed18/dotclaude/grill-me
handoffCompact the current conversation into a handoff document for another agent to pick up.npx shadcn@latest add KhaledSaeed18/dotclaude/handoff

Security

SkillDescriptionInstall
dependency-auditAudit a project's dependencies for outdated and vulnerable packages and surface breaking-change notes for upgrades. Works with any ecosystem, including npm/pnpm/yarn, pip/Poetry/uv, Cargo, Go modules, Maven/Gradle, Bundler, Composer, and others.npx shadcn@latest add KhaledSaeed18/dotclaude/dependency-audit
owasp-securityReview code being written or modified against the OWASP Top 10:2025 and ASVS secure-coding requirements, catching vulnerability classes before they ship. Works in any language or stack. Use when writing authentication or authorization logic, handling user input, adding API endpoints, choosing cryptographic operations, processing file uploads, or making any change that touches a trust boundary. Complements secret-scan (which finds credentials) and dependency-audit (which checks packages) with line-level vulnerability review.npx shadcn@latest add KhaledSaeed18/dotclaude/owasp-security
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. Use before committing, during review, or when auditing a repository.npx shadcn@latest add KhaledSaeed18/dotclaude/secret-scan

Testing

SkillDescriptionInstall
webapp-testingVerify a web application works correctly in a real browser using Playwright. Covers page navigation, form submission, user interactions, console error detection, screenshot capture, and responsive layout checking. Use when you need to confirm a UI feature actually works end-to-end, catch regressions after a change, verify a form flow completes, or check that the page is free of console errors. Requires Node.js; installs Playwright if not already present.npx shadcn@latest add KhaledSaeed18/dotclaude/webapp-testing

Version Control

SkillDescriptionInstall
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 called out. Conventional-Commits aware and Keep a Changelog formatted; respects any existing CHANGELOG or tooling. Use when preparing release notes or updating CHANGELOG.md.npx shadcn@latest add KhaledSaeed18/dotclaude/changelog
finish-branchWrap up a completed development branch by verifying tests pass, detecting the workspace state, then presenting clear merge / PR / keep / discard options and executing the chosen one safely — including correct worktree and branch cleanup. Use when implementation is done, tests should be green, and you need to integrate or put away the work.npx shadcn@latest add KhaledSaeed18/dotclaude/finish-branch
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 a conventional-commit message whose body explains why. Use when committing, branching, or pushing changes.npx shadcn@latest add KhaledSaeed18/dotclaude/git-commit
git-undoRecover safely from Git mistakes such as discard, unstage, amend, reset, revert, restore lost commits via reflog, recover deleted branches, and fix bad rebases. Chooses the least-destructive fix and protects against data loss. Use when something in Git went wrong and needs undoing.npx shadcn@latest add KhaledSaeed18/dotclaude/git-undo
git-worktreesSet up an isolated workspace for feature work so the current branch and working tree stay untouched — detecting existing isolation first, preferring the platform's native worktree tooling, and falling back to git worktrees only when nothing native exists. Use before starting feature work that needs isolation, or before executing an implementation plan.npx shadcn@latest add KhaledSaeed18/dotclaude/git-worktrees
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 be ignored. Flags secrets/build/dependency files that slipped into the repo. Use when creating, fixing, or auditing .gitignore.npx shadcn@latest add KhaledSaeed18/dotclaude/gitignore
merge-conflictResolve Git merge, rebase, cherry-pick, revert, and stash conflicts safely by understanding both sides and the operation in progress before integrating, then verifying the result builds and passes tests. Use when a merge/rebase/cherry-pick stops with conflicts or "needs merge".npx shadcn@latest add KhaledSaeed18/dotclaude/merge-conflict
pr-descriptionGenerate a clear, reviewer-friendly pull-request description from a diff, covering what changed, why, risk, and how it was tested. Use when opening a pull request or writing/improving a PR body.npx shadcn@latest add KhaledSaeed18/dotclaude/pr-description
release-tagCut a release by determining the SemVer bump from history, updating version files across any stack, refreshing the changelog, creating an annotated (optionally signed) Git tag, and pushing the release safely after pre-flight checks. Use when tagging a version, bumping the version, or preparing a release.npx shadcn@latest add KhaledSaeed18/dotclaude/release-tag

Agents

Engineering

AgentDescriptionInstall
architect-reviewerUse this agent when you need a design-level architecture review of a module, a proposed change, or an entire codebase. Evaluates module boundaries, coupling and cohesion, layering violations, scalability risk, and structural decisions that will become expensive to undo. Complements code-reviewer, which focuses on line-level correctness, by operating at the design level on shapes and relationships of components rather than individual functions. Use when designing a new service, refactoring a large module, evaluating a cross-cutting change, or when you want a second opinion on structural decisions before they harden.npx shadcn@latest add KhaledSaeed18/dotclaude/architect-reviewer
code-reviewerExpert reviewer for a code change (a diff, a staged set, a branch, or named files). Reviews for correctness, security, and maintainability across JavaScript/TypeScript stacks including React, Next.js, Node, Express, and NestJS. Use proactively after writing or modifying code, before opening a pull request, or when the user asks for a code review, a second pair of eyes, or feedback on a change.npx shadcn@latest add KhaledSaeed18/dotclaude/code-reviewer
debuggerUse this agent when you need to diagnose a bug, test failure, crash, or unexpected behavior through systematic root-cause analysis. Gathers evidence, forms and tests hypotheses, and delivers a confirmed root cause with a targeted fix recommendation. Does not guess or apply speculative patches. Use when a fix attempt has failed, when the bug is intermittent, when a stack trace needs tracing end-to-end, or when you want a second opinion on what is actually broken before touching code.npx shadcn@latest add KhaledSaeed18/dotclaude/debugger
error-detectiveUse this agent when you need to correlate errors, stack traces, and log entries across multiple services or files to find the root cause of an incident, a mysterious recurring error, or a failure that spans more than one component. Searches log files, cross-references timestamps, traces request IDs across service boundaries, and surfaces the originating cause rather than the downstream symptom. Distinct from the debugger agent, which traces bugs in source code; this agent works from runtime artifacts (logs, traces, crash dumps) and is most useful when the failure is happening in production or a staging environment where you cannot step through the code.npx shadcn@latest add KhaledSaeed18/dotclaude/error-detective
performance-engineerUse this agent when you need to investigate, measure, and resolve a performance problem end-to-end. Profiles the running system, identifies the actual bottleneck with numbers, designs or runs load tests, recommends targeted changes, and verifies the improvement is real. Use for slow API responses, high CPU or memory usage, database query latency, build-time regressions, or when preparing a service for increased load. Distinct from the performance-optimization skill, which provides the methodology; this agent can execute profiling tools, analyze their output, and iterate through the full measure-change-verify cycle.npx shadcn@latest add KhaledSaeed18/dotclaude/performance-engineer

Research

AgentDescriptionInstall
deep-researchIn-depth research agent for topics that need comprehensive, multi-source investigation with citations. Use when the user asks to research a topic thoroughly, gather and synthesize information from across the web, compare approaches or options, fact-check a claim against primary sources, or produce a sourced writeup or literature scan. For example, "research the current state of WebGPU adoption", "compare Postgres vs SQLite for an offline-first app, with sources", or "what does the evidence say about X, and where do experts disagree?"npx shadcn@latest add KhaledSaeed18/dotclaude/deep-research

Security

AgentDescriptionInstall
security-auditorUse this agent when you need a comprehensive security audit of a codebase, module, API surface, or pull request. Covers OWASP Top 10:2025, authentication and authorization logic, secret handling, input validation, dependency vulnerabilities, and supply-chain risk. Reports findings and concrete remediation steps without modifying code. Use before a production release, after adding auth or payment flows, when onboarding a new dependency, or when a security review is required before merge.npx shadcn@latest add KhaledSaeed18/dotclaude/security-auditor

Commands

Engineering

CommandDescriptionInstall
explain-codeWalk through a file, function, class, or module and explain what it does, how it works, and why it is structured the way it is. Suited for onboarding onto unfamiliar code, understanding a complex algorithm, or preparing to modify something you have not read before. Pass a file path or a symbol name as the argument.npx shadcn@latest add KhaledSaeed18/dotclaude/explain-code

Productivity

CommandDescriptionInstall
primeLoad project context into the session by reading key files and recent history. Primes the model with package metadata, architecture notes, recent commits, and directory structure so it can give better answers immediately. Use at the start of a session when switching to an unfamiliar repository or after a long break from a project.npx shadcn@latest add KhaledSaeed18/dotclaude/prime

Security

CommandDescriptionInstall
security-auditRun a full-codebase security audit covering OWASP Top 10:2025 vulnerability classes, authentication and authorization logic, secret handling, input validation, dependency CVEs, and supply-chain risk. Broader than the secret-scan skill, which scans a single diff. Produces a structured findings report ranked by severity. Pass a path to limit the audit to a specific module or directory.npx shadcn@latest add KhaledSaeed18/dotclaude/security-audit

Testing

CommandDescriptionInstall
write-testsGenerate a focused, production-quality test suite for a source file, detecting the project's existing test runner and conventions.npx shadcn@latest add KhaledSaeed18/dotclaude/write-tests

Version Control

CommandDescriptionInstall
clean-branchesList local Git branches that have been fully merged or are stale and delete them safely after showing what would be removed. Protects main, master, develop, and the currently checked-out branch. Pass --dry-run to preview without deleting anything. Distinct from the finish-branch skill, which closes a single active in-progress branch; this cleans up accumulated merged branches across the whole repository.npx shadcn@latest add KhaledSaeed18/dotclaude/clean-branches

Hooks

Observability

HookDescriptionInstall
tool-call-loggerA PreToolUse/PostToolUse hook that appends one JSON line per tool call (tool name, inputs, and response) to a local log file, with secret redaction and payload truncation. Use to audit, debug, or observe exactly what Claude Code did during a session.npx shadcn@latest add KhaledSaeed18/dotclaude/tool-call-logger

Security

HookDescriptionInstall
command-guardA PreToolUse hook that blocks catastrophic Bash commands before they run (recursive force deletes of the filesystem root or home, fork bombs, writing to or formatting raw disk devices, recursive chmod 777 on root, and force-pushes to main or master), returning a clear reason. Use to add a deterministic safety net against destructive shell commands.npx shadcn@latest add KhaledSaeed18/dotclaude/command-guard
injection-guardA UserPromptSubmit hook that scans incoming prompts for prompt-injection and jailbreak patterns (instruction overrides, system-prompt extraction attempts, role reassignments, DAN/developer-mode activations) before Claude processes them. Use to add a deterministic pre-Claude safety layer against injection attacks.npx shadcn@latest add KhaledSaeed18/dotclaude/injection-guard
sensitive-file-guardA PreToolUse hook that blocks Read, Edit, Write, and Bash operations that target sensitive files (.env, credentials, SSH private keys, certificates, secrets, AWS config, netrc, and similar). Use to prevent Claude from autonomously reading or exfiltrating credential files.npx shadcn@latest add KhaledSaeed18/dotclaude/sensitive-file-guard
smart-approveA PreToolUse hook that decomposes compound Bash commands (&&, ||, ;, |, $(), backticks) into their component sub-commands and checks each one independently against a deny list, closing the chain-smuggling gap where a dangerous operation is embedded inside a safe-looking command chain. Use to upgrade command-guard with compound-command awareness.npx shadcn@latest add KhaledSaeed18/dotclaude/smart-approve

License

MIT © Khaled Saeed

Attributions

Some items in this project were created from scratch, while others were inspired by, adapted from, or built upon work from the open-source community. Credit and thanks to the following resources:

SourceLinkItems inspired by
Matt Pocock's Skillsmattpocock/skillsskills
Obra's Superpowersobra/superpowersskills
Anthropic's Skillsanthropics/skillswebapp-testing
Addy Osmani's Agent Skillsaddyosmani/agent-skillsperformance-optimization
Alirezarezvani's Claude Skillsalirezarezvani/claude-skillsadversarial-reviewer
Agamm's Claude Code OWASPagamm/claude-code-owaspowasp-security
QdHenry's Claude Command Suiteqdhenry/Claude-Command-Suiteprime, explain-code, security-audit, clean-branches
VoltAgent's SubagentsVoltAgent/awesome-claude-code-subagentsdebugger, security-auditor, architect-reviewer, performance-engineer, error-detective
Wshobson's Agentswshobson/agentsdebugger, security-auditor, architect-reviewer, performance-engineer, error-detective
Disler's Hooks Masterydisler/claude-code-hooks-masterysensitive-file-guard, injection-guard
Rohitg00's Toolkit (via liberzon/claude-hooks)rohitg00/awesome-claude-code-toolkitsmart-approve
Ver o original no GitHub

Bom para

Relacionados