agentleFS
aborroyaborroy/aiup-alfresco/skills/audit-config-validator/SKILL.md

audit-config-validator

Skill14 starsChanged 5 months agoApache-2.0View on GitHub

Validates custom Alfresco audit application XML for well-formedness, correct audit model namespace, application key matching the enable property, and every RecordValue dataExtractor/dataGenerator referencing a declared and registered bean. Trigger automatically after generating or editing a *-audit.xml or an audit *DataExtractor.java / *DataGenerator.java file.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    FLAG as ERROR: if no audit.{app-key}.enabled property is present in a companion .properties file matching the key exactly.

    line 18
  2. Very specific:

    WARN: if audit.enabled=true (the master switch) is not present anywhere in the project.

    line 21
  3. Very specific:

    Every <RecordValue dataExtractor="X"> must reference a <DataExtractor name="X" ...> declared in <DataExtractors>.

    line 24
  4. Very specific:

    If a *DataExtractor.java exists, it must extends AbstractDataExtractor and implement isSupported and extractData.

    line 34
  5. Very specific:

    If a *DataGenerator.java exists, it must extends AbstractDataGenerator.

    line 36
  6. Very specific:

    WARN: if <PathMappings> is absent while dataSource paths reference a producer path that is not mapped into the application namespace.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit Config Validator

Validate the given custom Alfresco audit application against these rules.

XML Structure Validation

  • The audit XML must be well-formed and its root <Audit> element must declare the audit model namespace http://www.alfresco.org/repo/audit/model/3.2.
  • There must be exactly one <Application> with both name and key attributes.

Application Key / Enable Consistency

  • The <Application key="{app-key}"> value must be lowercase and prefix-scoped.
  • FLAG as ERROR if no audit.{app-key}.enabled property is present in a companion .properties file matching the key exactly.
    • Why it breaks: the application is defined but never enabled, so nothing is recorded.
  • WARN if audit.enabled=true (the master switch) is not present anywhere in the project.

Extractor / Generator Wiring

  • Every <RecordValue dataExtractor="X"> must reference a <DataExtractor name="X" ...> declared in <DataExtractors>.
  • Every <RecordValue dataGenerator="Y"> must reference a <DataGenerator name="Y" ...> declared in <DataGenerators>.
  • For each custom (non-built-in) <DataExtractor registeredName="...">, there must be a Spring bean whose registeredName property matches, with parent="auditModelExtractorBase".
    • FLAG as ERROR a registeredName with no matching bean (the application fails to register or records nothing).

Java Extractor Validation

  • If a *DataExtractor.java exists, it must extends AbstractDataExtractor and implement isSupported and extractData.
  • If a *DataGenerator.java exists, it must extends AbstractDataGenerator.

Registration Validation

  • The audit model must be registered via an AuditModelRegistrationBean (init-method="registerModel") whose auditModelUrl points at the audit XML on the classpath.
  • The registering context must be imported from module-context.xml.
  • WARN if <PathMappings> is absent while dataSource paths reference a producer path that is not mapped into the application namespace.

Output

Report all violations with file path, line number, rule violated, and suggested fix. If no violations found, confirm the audit application is valid.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.