AGENTS.md

General rules

1. Add only new files to git. Do not modify the existing staging unless explicitly required.

Verification development stages

1. Implement everything in pure Kotlin, making full use of IDE-assisted language features and inspections.
2. Add inspection messages and tooltips to SecurityPluginBundle.properties.
3. Create the inspection draft in the technology-specific folder under securityLinter.
4. Add tests covering the inspection:
   • Example of a Docker inspection: DS003SshPortExposed.kt
   • Example of test data for Docker inspections: DS003
   • Example of extended test data with additional cases: DS029
5. Create an inspection description in HTML using the same filename as the inspection class in inspectionDescriptions.
6. Register the inspection in XML:
   • For YAML-based inspections: dev.protsenko.security-linter-yaml.xml
   • For general and Docker-based inspections: plugin.xml
7. If the inspection validates Docker RUN commands, follow the rules defined in RunCommandValidator.kt.
   • Register the required extension points in plugin.xml.
8. If the inspection is YAML-based, use the bundled helper classes such as YamlPath.kt.
9. Ensure that all tests pass.
10. If the plugin version has not been updated in gradle.properties, update it.
11. Update the changelog in CHANGELOG.md.
12. Perform a full build and run the complete test suite for the plugin.

Summary for verification development

1. All inspections must be registered and covered by tests.
2. All inspections must leverage Kotlin and IDE capabilities effectively.
3. All reusable helper utilities should be covered by JUnit 3 tests.
4. All inspections must cover corner cases and include extended test scenarios.