From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

I'd say it depends.
`buildKotlinToolingMetadata` means "build the kotlin tooling metadata"
`publishToMavenLocal` means "publish to maven local"
But
`checkSpotless` would mean "check spotless", not what it should mean "check my code with spotless". So it would more be `doSpotlessCheck`or to be more succinct `spotlessCheck`. An alternative could be `checkWithSpotless`, but it somehow feels more bulky.

So generally I like it more like `compileJava` and friends, but only if it makes sense and `checkSpotless` would imho not as it would be ambiguous and easily interpreted wrongly.

Task registrations should start with a verb. Task type names should be nouns *not* ending with Task. e.g.
`compileJava` and `JavaCompile`

I'm curious <@UF9HQE743>, would you have called it `checkSpotless`?

no, I agree with you that that would sound like it would be checking spotless.
For check tasks Gradle uses the convention to use the checker as a verb combined with what it is checking, e.g. `checkstyleMain` so I guess I would go with `spotbugsMain`

So `spotlessMain` then, yeah. :slightly_smiling_face:

While I'm still not sure I like that inconsistency.
In most other cases `main` is left out and only added for all other source sets.