devteam

Plugin devteam from marketplace my-claude-devteam in NYCU-Chung/my-claude-devteam. Commands read from the repo's manifest — 1 month ago.

Subagents (14)

• README
• README.zh-TW
• critic

  Code reviewer and security auditor. Hunts for bugs, security holes, logic errors, edge cases, performance issues, and inconsistencies. Every finding with file path + line number. Use before every commit, deploy, or merge. Also handles deep security review (hardcoded secrets, injection, XSS, path tra

• db-expert

  Database expert: schema design, migration safety, query optimization, index advice. Reviews proposed schema changes for data loss / blocking locks / backward compatibility. Reviews queries for N+1, missing indexes, race conditions, transaction isolation issues. Read-only — analyzes and reports, neve

• debugger

  Debug engineer and log analyst. Systematically finds the root cause of bugs: reads logs, narrows scope, builds hypotheses, verifies, fixes. Also analyzes PM2 / Docker / systemd / Nginx logs for error patterns. Use for any bug, service outage, test failure, or unexpected behavior. Never guesses — alw

• frontend-designer

  Frontend designer who builds memorable UIs: landing pages, dashboards, components. Rejects generic AI slop, commits to a bold aesthetic direction, ships production-quality code. Use for new pages, UI redesigns, and visual upgrades.

• fullstack-engineer

  Senior full-stack engineer operating the P7 methodology: read reality → design solution → impact analysis → implement → three-question self-review → [P7-COMPLETION] delivery. Ships features across frontend, backend, and DevOps. Use for single-feature implementation and cross-module changes.

• migration-engineer

  Framework / library / language version upgrades. Handles breaking changes, deprecation removals, major-version bumps. Reads the upstream changelog, audits every usage of changed APIs, executes the upgrade incrementally with verification at each step. Use for Next.js 13→14, Vue 2→3, Tailwind 3→4, Rea

• onboarder

  Codebase explorer for first-time exploration. Builds a mental model of an unfamiliar codebase: architecture, entry points, key modules, external dependencies, suspicious areas. Read-only. Use when joining a new project, evaluating an open-source repo before contributing, or auditing a repo you haven

• planner

  Tech lead operating the P9 methodology. Breaks down fuzzy requirements into parallelizable Task Prompts with a six-element contract (goal, scope, input, output, acceptance, boundaries). Use before complex tasks touching 3+ files or 2+ modules. Never writes code — output is prompts, not implementatio

• refactor-specialist

  Large-scale safe refactoring: rename across many files, extract module, move files, restructure folders. Differs from fullstack-engineer by being more cautious, scoped, and verification-heavy. Use for refactors that touch 10+ files where regression risk is real.

• tool-expert

  Tool expert who picks the right tools, chains complex workflows, and troubleshoots tool failures. Knows when to use built-in tools vs MCP servers vs shell commands. Use for complex tool chaining, MCP server issues, or when you're unsure which tool fits the job.

• vuln-verifier

  Vulnerability verifier. Takes the critic's findings and writes actual PoC code to prove each vulnerability is real (or a false positive). Produces verification reports suitable for security advisories, issues, and PRs. Use AFTER critic flags a suspected security issue.

• web-researcher

  Technical documentation researcher. Looks up API specs, official docs, error codes, version differences, and library usage. Search-only — never writes code, never modifies files. Use whenever the team needs ground truth from the web and you're tired of guessing.

Hooks (21)

• PreToolUse

  input=$(cat | jq -r '.input // empty'); if echo "$input" | grep -qE 'rm\s+(-[a-zA-Z]*r[a-zA-Z]*f|--recursive.*--force|-rf)'; then echo 'BLOCKED: rm -rf is dangerous' >&2; exit 2; fi; exit 0

• PreToolUse

  input=$(cat | jq -r '.input // empty'); if echo "$input" | grep -qE 'git\s+push.*(-f|--force).*\s+(main|master)'; then echo 'BLOCKED: Force pushing to main/master is not allowed.' >&2; exit 2; fi; exi

• PreToolUse

  node -e "let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{const i=JSON.parse(d);const cmd=i.tool_input?.command||'';if(/--no-verify/.test(cmd)){process.stderr.write('[devteam] BLO

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/branch-protection.js

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/commit-quality.js

• PreToolUse

  filepath=$(cat | jq -r '.file_path // .filePath // empty'); if echo "$filepath" | grep -qE '\.(env|pem|key)$|/secrets/|credentials'; then echo "BLOCKED: Cannot modify sensitive file: $filepath" >&2; e

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/config-protection.js

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/suggest-compact.js

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/mcp-health.js pre

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/large-file-warner.js

• PostToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/log-error.sh

• PostToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/audit-log.js

• PostToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/accumulator.js

• PostToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/design-quality.js

• PostToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/test-runner.js

• PostToolUseFailure

  node ${CLAUDE_PLUGIN_ROOT}/hooks/mcp-health.js failure

• Stop

  node ${CLAUDE_PLUGIN_ROOT}/hooks/batch-format.js

• Stop

  node ${CLAUDE_PLUGIN_ROOT}/hooks/check-console.js

• Stop

  node ${CLAUDE_PLUGIN_ROOT}/hooks/cost-tracker.js

• Stop

  node ${CLAUDE_PLUGIN_ROOT}/hooks/session-summary.js

• SessionStart

  echo '[devteam] Dev team online — 12 agents + 15 hooks active. Three red lines: closure discipline, fact-driven, exhaustiveness.' >&2; exit 0

Similar plugins