maven-plugin-configuration
Use when configuring Maven plugins, setting up common plugins like compiler, surefire, jar, or creating custom plugin executions.
Use when configuring Maven plugins, setting up common plugins like compiler, surefire, jar, or creating custom plugin executions.
Use when configuring artifacts for inter-job data passing or caching for faster builds. Covers cache strategies and artifact management.
Use when building and deploying Expo apps with EAS Build. Covers build configuration, development builds, production builds, and app store submission.
Deploy systematic liberation technology - Gunasthanas, Kevala Jnana, Tirthankara navigation active.
Use when working with Maven build phases, goals, profiles, or customizing the build process for Java projects.
Use when ruboCop configuration including YAML config, departments, inheritance, and customization.
Use when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.
Use when managing Maven dependencies, resolving dependency conflicts, configuring BOMs, or optimizing dependency trees in Java projects.
Autonomous plan execution - fresh subagent per task with automated code review between tasks. No human-in-loop, high throughput with quality gates.
Skill testing methodology - run scenarios without skill (RED), observe failures, write skill (GREEN), close loopholes (REFACTOR).
Gate 4 of development cycle - dispatches 5 specialized reviewers (code, business-logic, security, test, nil-safety) in parallel for comprehensive code review feedback.
Evidence-first completion gate - requires running verification commands and confirming output before making any success claims.
This skill should be used when running CI checks iteratively and fixing failures. Use when executing make targets (fast-ci, all-ci, ci), iterating on lint/format/type/test errors, or needing the devrun agent pattern for pytest/ty/ruff/prettier/make/gt commands.
Process for capturing qualitative feedback and injecting it into CS playbooks.
Use when validating automation builds before launch or after significant changes.
Use to queue practice reps, certifications, and accountability cadences after coaching sessions.
Use to enforce stage definitions, next-step requirements, and data completeness across the pipeline.
Use when structuring paid media campaigns/ad sets to balance testing, delivery, and optimization constraints.
Use when running launch command centers, standups, and escalation workflows.
Validate and release Navigator plugin to marketplace. Auto-invoke when user says "release plugin", "publish navigator", "create release", or "deploy new version".
Use to enforce approvals, compliance, and auditability for personalization programs.
Use when managing asset metadata, dependencies, and delivery workflows across teams.