alfresco-migrator-agent
Skill14 starsChanged 5 months agoApache-2.0View on GitHub
Analyses an existing Alfresco AMP or JAR extension, identifies deprecated APIs and outdated patterns, and produces a migration plan with concrete code diffs.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/aiup-alfresco.mdcCursor rule
- aca-extensionSkill
- actionsSkill
- aikauSkill
- aiup-alfrescoSkill
- alfresco-architect-agentSkill
- alfresco-debugger-agentSkill
- audit-config-validatorSkill
- auditSkill
- behavioursSkill
- bootstrap-loaderSkill
- content-modelSkill
- content-model-validatorSkill
- content-storeSkill
- docker-compose-healthcheck-injectorSkill
- docker-composeSkill
- event-api-topology-checkerSkill
- eventsSkill
- metadata-extractorSkill
- migration-advisorSkill
- permission-aware-query-builderSkill
- permission-model-validatorSkill
- permissionsSkill
- repository-patchSkill
- requirementsSkill
- rest-apiSkill
- rest-api-validatorSkill
- rule-conditionsSkill
- scaffoldSkill
- scheduled-jobsSkill
- sdk-version-detectorSkill
- share-configSkill
- subsystemSkill
- surfSkill
- testSkill
- transformsSkill
- web-scriptsSkill
- workflow-bpmn-validatorSkill
- workflowSkill
- audit-config-validatorSkill
- content-model-validatorSkill
- docker-compose-healthcheck-injectorSkill
- event-api-topology-checkerSkill
- migration-advisorSkill
- permission-aware-query-builderSkill
- permission-model-validatorSkill
- rest-api-validatorSkill
- sdk-version-detectorSkill
- workflow-bpmn-validatorSkill
The file
Files
Alfresco Migrator Agent
You are an Alfresco migration specialist. You analyse existing extensions and produce actionable migration plans.
Process
- Scan the project — identify all Java classes, Spring config, content models, Web Scripts
- Detect SDK version — invoke
sdk-version-detectorskill - Find deprecated APIs — invoke
migration-advisorskill - Assess packaging — AMP to JAR migration if needed
- Check content model compatibility — invoke
content-model-validatorskill - Produce migration plan with prioritised steps and effort estimates
Output: Migration Plan
# Migration Plan: {Project Name}
## Current State
- SDK version: {detected}
- ACS target: {detected}
- Packaging: {AMP/JAR}
- Java version: {detected}
## Migration Steps (ordered by priority)
### 1. {Step title}
- **Effort**: trivial / moderate / significant
- **Files affected**: {list}
- **Before**: {code snippet}
- **After**: {code snippet}
- **Risk**: {description}
## Breaking Changes
{List of changes that require testing}
## Recommended Test Plan
{Specific tests to validate the migration}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

