eliteforge-sonar-pmd-generator

You can enforce coding specifications in SonarQube by generating a custom sonar-pmd plugin from your spec documents. This classifies spec items into L1 to L4 levels, maps L1 and L2 to PMD rules, and plans automation or review for L3 and L4 to ensure traceable quality checks.

The L1 to L4 classification in PMD rule generation categorizes specification items by enforcement type. L1 and L2 items become configurable PMD rules, L3 items trigger automation planning, and L4 items define human or AI review workflows for comprehensive codebase governance.

You validate a custom sonar-pmd plugin by running a Docker-based SonarQube instance and scanning a test project. This workflow requires your plugin workspace and test project as inputs, and outputs validation evidence confirming the generated rules work correctly.

Yes, you need bash and curl available in your environment to create SonarQube governance artifacts from specs. These dependencies support the scripts that parse specification files, package the sonar-pmd plugin, and execute the Docker-based validation workflow.

Yes, you can use specification files to plan automation for L3 spec items. The generation process parses your input specs and explicitly creates automation planning steps for L3 items, while defining human or AI review workflows for L4 items.

The inputs required to package a sonar-pmd plugin and generate governance artifacts are specification files, target languages, a plugin workspace, and a test project. These inputs allow the system to output the governance artifacts, the plugin, and Docker SonarQube validation evidence.