By edonghyun
Delegated browser QA operator: plan, run, monitor, triage, and optionally repair acceptance checks from requirements with evidence dashboards.
Serve or open the qa-operator live dashboard. Use when the user wants to monitor QA progress, see a dashboard, watch run status, view screenshots as they appear, or continue an existing QA dashboard; triggers include "monitor 켜줘", "대시보드 열어줘", "진행상황 보여줘", "QA dashboard", "live monitor", "실시간으로 보고싶어". Reads manifest.json, qa-plan.json, and runs/latest or latestRun qa-results.json; writes no QA results.
Convert requirements into a qa-operator plan. Use when the user provides a spreadsheet, issue list, PR, current diff, feature checklist, staging URL, or range and wants browser QA planned before execution; triggers include "QA 계획", "qa-plan.json", "요구사항 정리", "시트 범위 QA", "테스트 케이스로 바꿔줘", "plan QA", "acceptance plan". Writes artifacts/qa-operator/SLUG/qa-plan.json, manifest.json, index.html, and an initialized run skeleton. Do not use when the user only wants to run an already existing plan.
Fix scoped, verifiable local defects found by qa-operator and rerun affected QA items. Use when the user explicitly allows repair, asks to "고치고 재검증", "명백한 버그는 수정", "auto repair local bugs", "fix failed QA", or "repair and retest". May modify application code only for narrow defects, writes repair-log.md, updates qa-results.json, and reruns affected items. Do not use for product decisions, production writes, destructive data actions, broad redesign, or ambiguous UX preferences.
Execute browser QA from an existing qa-plan.json and update evidence incrementally. Use when the user wants server access, login, feature checks, validation, screenshots, traces, console/network logs, UI/UX risk scanning, or retry of failed items; triggers include "브라우저로 QA 실행", "직접 확인해줘", "QA run", "실행하면서 결과 업데이트", "스크린샷 남겨줘", "FAIL만 재검증", "run browser QA". Writes only runs/RUN_ID/qa-results.json, screenshots, traces, logs, and summary files under artifacts/qa-operator/SLUG/ unless paired with repair.
Default delegated QA entry for qa-operator. Use when the user wants to hand off QA from a requirement source, spreadsheet, issue, PR, feature list, current diff, or staging URL; triggers include "QA 맡겨줘", "완전 QA 돌려줘", "브라우저로 직접 확인해줘", "제대로 구현됐는지 확인해줘", "UI/UX 문제까지 찾아줘", "monitor 켜고 진행상황 보여줘", "실패 항목 재검증해줘", "run QA", "browser QA", "delegated QA". Writes a qa-operator artifact tree under artifacts/qa-operator/SLUG/ and routes to plan, monitor, run, triage, and optional repair. Do not use for pure code review with no browser or acceptance evidence requirement.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A host-neutral personal plugin marketplace for coding agents, focused on safety nets — plugins that keep code, spec, tests, and team knowledge in sync rather than generating net-new content.
Read
docs/PHILOSOPHY.mdfor the mission,docs/CONVENTIONS.mdfor the rules every plugin follows, anddocs/CONTRIBUTING.mdto add a new plugin or skill.
# Add marketplace from GitHub.
claude plugin marketplace add edonghyun/donghyuns-agent-tools
# Or, during local development.
claude plugin marketplace add /Users/idonghyeon/projects/donghyuns-agent-tools
# Install plugins.
claude plugin install spec-mirror@donghyuns-agent-tools
claude plugin install qa-operator@donghyuns-agent-tools
claude plugin install feature-intake@donghyuns-agent-tools
# Refresh after marketplace changes.
claude plugin marketplace update donghyuns-agent-tools
claude plugin update qa-operator@donghyuns-agent-tools
claude plugin update feature-intake@donghyuns-agent-tools
Codex support reuses the same plugins/<plugin>/skills/ tree and adds Codex-specific manifests next to the Claude manifests:
.agents/plugins/marketplace.jsonplugins/<plugin>/.codex-plugin/plugin.json# Add marketplace from GitHub.
codex plugin marketplace add edonghyun/donghyuns-agent-tools --ref main
# Or, during local development.
codex plugin marketplace add /Users/idonghyeon/projects/donghyuns-agent-tools
# Install Codex-supported plugins.
codex plugin add qa-operator@donghyuns-agent-tools
codex plugin add feature-intake@donghyuns-agent-tools
# Refresh after marketplace changes.
codex plugin marketplace upgrade donghyuns-agent-tools
codex plugin add qa-operator@donghyuns-agent-tools
codex plugin add feature-intake@donghyuns-agent-tools
Start a new Codex thread after install or update so the refreshed plugin skills are loaded into the session.
Turn external feature artifacts into product integration analysis packages. feature-intake takes VoC-driven PoCs, demo apps, Figma prototypes, internal tools, AI experiments, or screenshots from another team and produces screenshot-backed user flows, user journeys, use cases, product framing, integration fit, risks, MVP boundaries, and handoff documentation.
Just say:
이 PoC를 feature-intake 해줘. 스크린샷 포함해서 유저플로우, 유저저니, 유즈케이스, 제품 편입 분석까지 정리해줘.
Skills:
| Command | Description |
|---|---|
/feature-intake:start | Natural-language entry. Runs inspect, capture, framing, analysis, mapping, and packaging. |
/feature-intake:inspect | Discover artifact structure, pages, controls, external calls, and capture targets. |
/feature-intake:capture | Capture page, interaction, modal/dialog, edge-case, and contact-sheet screenshots. |
/feature-intake:frame | Generalize product framing: actors, placement, output, quality bar, MVP, data/AI/storage, operations, risks. |
/feature-intake:analyze | Write user flows, journeys, use cases, inventories, and screen-by-screen annotations. |
/feature-intake:map | Map the artifact into the existing product's IA, modules, data, APIs, permissions, storage, and backlog. |
/feature-intake:package | Assemble the final screenshot-backed handoff README and coverage matrix. |
Workflow:
/feature-intake:start
├─ inspect
├─ capture
├─ frame
├─ analyze
├─ map
└─ package
Plugin docs: CONCEPTS · WORKFLOW-GUIDE · EXAMPLES · TROUBLESHOOTING
Delegate browser QA from natural language. qa-operator turns requirement lists, spreadsheets, issues, PRs, or feature ranges into a QA plan, starts a live monitor dashboard, executes browser checks, captures screenshots/logs/traces, flags UI/UX risks, triages failures, and can repair obvious local defects when allowed.
Just say:
이 시트 31~43번 QA 맡겨줘. monitor 켜고 UI/UX 문제까지 봐줘.
Skills:
npx claudepluginhub edonghyun/donghyuns-agent-tools --plugin qa-operatorEvidence-backed UI iteration operator for comparing baseline and current web, mobile web, native mobile, and local session-derived UI states during product UI changes.
Turn external feature artifacts, PoCs, demos, prototypes, and VoC experiments into screenshot-backed page-walk product integration analysis packages.
Generate, drift-check, lint, test-stub, coverage-audit and scope-walk E2E specs against the current implementation. A six-skill safety net for keeping code, spec, tests, and team knowledge in sync.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Create new skills, improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, or benchmark skill performance with variance analysis.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development