From aiup-alfresco
Validates custom Alfresco audit application XML structure, DataExtractor/DataGenerator bean wiring, Spring bean registration, and Java class conventions for Alfresco audit configs.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aiup-alfresco:audit-config-validatorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate the given custom Alfresco audit application against these rules.
Validate the given custom Alfresco audit application against these rules.
<Audit> element must declare the audit model
namespace http://www.alfresco.org/repo/audit/model/3.2.<Application> with both name and key attributes.<Application key="{app-key}"> value must be lowercase and prefix-scoped.audit.{app-key}.enabled property is present in a companion
.properties file matching the key exactly.
audit.enabled=true (the master switch) is not present anywhere in the project.<RecordValue dataExtractor="X"> must reference a <DataExtractor name="X" ...>
declared in <DataExtractors>.<RecordValue dataGenerator="Y"> must reference a <DataGenerator name="Y" ...>
declared in <DataGenerators>.<DataExtractor registeredName="...">, there must be a Spring
bean whose registeredName property matches, with parent="auditModelExtractorBase".
registeredName with no matching bean (the application fails to register
or records nothing).*DataExtractor.java exists, it must extends AbstractDataExtractor and implement
isSupported and extractData.*DataGenerator.java exists, it must extends AbstractDataGenerator.AuditModelRegistrationBean
(init-method="registerModel") whose auditModelUrl points at the audit XML on the classpath.module-context.xml.<PathMappings> is absent while dataSource paths reference a producer path that
is not mapped into the application namespace.Report all violations with file path, line number, rule violated, and suggested fix. If no violations found, confirm the audit application is valid.
npx claudepluginhub aborroy/aiup-alfrescoValidates Alfresco content model XML files for namespace format, type/aspect declarations, property data types, and reserved prefix usage. Automatically activates when editing *-model*.xml or *-context.xml files.
Validates application configurations by scanning JSON, YAML, TOML, env files; creates schemas, tests for security issues, consistency, and errors across environments.
Validates 1C configuration XML files for structural errors after creation or modification. Checks XML well-formedness, properties, enums, and object directories.