메뉴
Orchestrates JM-ADK Alfa repository maintenance in fixed safety phases: bootstrap, repo sync audit, local state preservation, isolated branch planning, selective import or consolidation planning, cleanup planning, validation gates, and closeout blockers.
Redacta agradecimientos post-proceso diferenciados por persona, evidencia de interaccion, voz de marca y lint offline contra FOMO, hustle, servilismo y promesas no verificables.
Optimiza CV y carta de presentacion para ATS, rol objetivo y voz de marca con lint offline de keywords, secciones, longitud, contacto y tono.
Cosecha aprendizajes, valida evidencia y produce un cierre de conversacion reproducible con handoff, riesgos y plan de actualizaciones durables.
Validates plugin directory layout against the official Claude Code plugin spec. Triggers: validate structure, check layout, directory audit, plugin skeleton check.
Validates frontmatter and body structure of all skills, agents, and commands in a plugin. Triggers: validate components, check frontmatter, component audit, skill validation.
Use when the user asks to "scan for secrets", "detect credentials", "sanitize sensitive data", "check for exposed passwords", "run security gate G0", or mentions secret detection, credential scanning, security gate G0, sensitive data masking, API key exposure, token detection.
| name | alfa-repo-maintenance-orchestrator |
| version | 1.0.0 |
| description | Orchestrates JM-ADK Alfa repository maintenance in fixed safety phases: bootstrap, repo sync audit, local state preservation, isolated branch planning, selective import or consolidation planning, cleanup planning, validation gates, and closeout blockers. |
| owner | JM Labs |
| triggers | ["alfa repo maintenance","repo sync cleanup orchestrator","alfa cleanup workflow","systematic repo update","maintenance branch plan"] |
| allowed-tools | ["Read","Glob","Grep","Bash","Write"] |
Use this skill for JM-ADK Alfa maintenance when the work includes repo sync, local cleanup, skill import, branch consolidation, generated index refresh, or PR preparation.
Always execute and report these phases in order:
bootstraprepo-sync-auditlocal-state-preservationbranch-planimport-consolidation-plancleanup-planvalidation-gatescloseoutThe report contract lives in assets/orchestration-report-contract.json; the offline checker is scripts/validate_alfa_maintenance_orchestration.py.
Writes are blocked until all of these are true:
main, HEAD, upstream, and status.main branch for any mutating phase.no_push and no_main_merge remain true unless the user explicitly changes the policy.Use assets/write-blocker-policy.json to classify blockers.
Coordinate these skills by contract, even when they are implemented in separate PRs:
repo-sync-auditor: read-only baseline, remote, branch, and drift evidence.local-state-preservation: mandatory preservation packet before mutation.workspace-governance: allowed workspace/archive locations and transient file policy.git-workflow: isolated branches, no direct main, no unsafe resets.safe-scripting-and-bash: defensive shell execution and dry-run bias.quality-gatekeeper: validation gates and closeout decision.tasklog-management: work log, branch intent, and progress evidence.session-end-cleanup: final state, residual risks, and next actions.See assets/integration-matrix.json.
The validation phase must include at minimum:
git status --short --branch
bash scripts/check-repo-boundaries.sh
python3 scripts/count-components.py --check-docs
python3 scripts/validate-skills.py --strict
python3 scripts/validate-skill-dod.py --skill <skill>
python3 scripts/validate-skill-scripts.py --strict --run-checks --skill <skill>
python3 scripts/validate-skill-scripts.py --strict --run-checks
python3 scripts/validate-runtime-instructions.py
python3 scripts/check-devkit-readiness.py
git diff --check main...HEAD
Use assets/validation-gates.json for machine-checkable gate names.
Produce:
scripts/validate_alfa_maintenance_orchestration.py.templates/output.md.local-state-preservation as a dependency even when implemented in a prior branch.If a required phase cannot pass, set next_action to blocked or pause and record the reason. Do not reinterpret a missing preservation manifest as a warning when a mutating phase is planned.