Plugin Workflow
Developmentplugin-workflowPlugin Workflow is an Agent Skill for development published in the erxes/erxes repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Baseline workflow for erxes plugin contributions. Use for frontend or backend plugin changes to enforce local discovery, minimal scope, validation, and diff review.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/erxes/erxes/blob/HEAD/.agents/skills/plugin-workflow/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/plugin-workflow, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Skill: Plugin Contribution Workflow
Before Coding
- Read the root
AGENTS.mdand any nestedAGENTS.mdthat applies to the touched path - Understand plugin structure
- Find similar implementation
- Reuse existing patterns
During Coding
- Keep changes scoped
- Preserve architecture
- Preserve UX consistency
- Avoid unnecessary abstractions
- Keep components understandable
After Coding
- Run
pnpm nx lint <plugin> - Run
pnpm nx build <plugin> - Run
pnpm nx test <plugin>when tests, test setup, or tested behavior were touched - Fix introduced warnings
- Remove debug code
- Review final diff
After Pushing / PR
- Run
pr-review-loopskill. The erxes repo uses AI reviewers (CodeRabbit, Sourcery, Claude Code Action, Kimi, SonarCloud). After every commit to a PR, you MUST poll for new comments, address every actionable item, wait for CI checks to pass, and loop until zero open comments and all checks green. Only then is the task done. Do not declare a task complete while PR comments are unresolved or CI is failing.
Engineering Expectations
- Consistency over cleverness
- Reuse over reinvention
- Minimalism over overengineering
- Repository patterns over personal preference