个人作者
Dragan Filipović
Agentic SDLC platform in production. I build agent-ready codebases. AEM MCP Server author.
- Skills
- 79
- 仓库
- 1
- 职业覆盖
- 6
- 场景覆盖
- 6
- Stars
- ★ 7
Dragan Filipović 的 Skills 79
dx-hub-status
Show hub dispatch status — which repos are running, done, blocked or failed. Use for 'hub status', 'what's running'.
dx-hub-init
Initialize a hub directory for multi-repo orchestration. Discovers sibling repos, merges configs, validates CLI compatibility. Use when setting up hub mode for the first time. Trigger on "init hub", "set up hub", "multi-repo setup".
dx-hub-dispatch
Dispatch a ticket to several repos — open an independent Claude session per repo in VS Code terminals. Use for 'hub dispatch', 'work on ticket across repos'.
dx-hub-config
View and edit hub configuration — add repos, adjust terminal delay. Use to manage hub settings. Trigger on "hub config", "add repo to hub", "terminal delay".
dx-discover-repos
Resolve which repos a work item touches (explicit directive → simple block → cross-repo table → LLM). Used by the KAI-HUB router to fan an agent out across repos; 'which repos'.
dx-upgrade
Upgrade a consumer project to the installed plugin versions — run dx-doctor, fix stale and missing files, list manual actions. Use after upgrading plugins.
dx-ticket-analyze
Research an ADO/Jira ticket and list the source files and assets it involves. Use for 'analyze ticket', 'what files does this touch?', 'find files for this story'.
dx-sync
Sync plugin updates to consumer repos — runs sync-consumers.sh with selected repos and options. Use when you say "sync plugins", "update consumers", "push to all repos".
dx-step
Execute the next pending step in implement.md — implement, test, review, commit, update status. Use to go one step at a time ('next step').
dx-step-verify
6-phase pre-PR verification with auto-fix — compile, lint, test, secrets, architecture, code review (max 3 cycles). Use after /dx-step-build. Not for checks on a running AEM (aem-verify, aem-fe-verify, aem-qa) or existing PRs (dx-pr-review).
dx-step-fix
Diagnose and fix a blocked step — compile error, test failure, review rejection — directly or by adding corrective steps to implement.md. Use when /dx-step fails.
dx-step-build
Build and deploy to the local dev environment, fixing errors until the build passes. Use after code changes ('build', 'compile', 'build and deploy').
dx-step-all
Run every plan step hands-free (implement, test, review, commit), with step-fix on failures; stops after 2 failed fixes on one step. Use for 'execute plan', 'run all steps'.
dx-simplify
Simplify working code without changing its behavior — Chesterton's Fence, Rule of 500. Use for 'simplify', 'reduce complexity', 'refactor for clarity'.
dx-simple
Apply a small AEM change (a11y label, color, spacing, copy, CSS class, icon, focus trap) via authoring (JCR) or code (PR) paths, read from the ADO story. Use for 'simple change', 'small tweak', '@kai-simple'.
dx-security
Security audit — OWASP Top 10, secrets scan, dependency audit, input validation, auth review. Use before a PR or when code handles user input, auth or external integrations.
dx-scan
Deep project scan — discover conventions from actual code, customize rule files with real values, and generate seed data. Interactive. Run after /dx-init + /dx-adapt + /aem-init. Use when setting up a new project or when project structure changes significantly.
dx-req
Start any ticket — fetch the ADO/Jira story, check DoR, distill requirements, research the codebase, write a team summary. Not for requirements from a file (/dx-req-import), child Tasks (dx-req-tasks) or DoD (dx-req-dod).