agentleFS
marslomarslo/skills/.cursor/rules/groovy-implicit-return.mdc

skills / rules

Cursor rule0 starsChanged 2 months agoMITView on GitHub

Groovy supports implicit returns (the last expression in a method is the return value). Do not flag or suggest adding explicit return statements to Groovy methods.

The file

We split this groovy-implicit-return.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    Never warn about or add return keywords to satisfy a "missing explicit return" linter hint in Groovy code.

    line 13
  2. Very specific:

    Do not treat the absence of a return keyword as a bug or style violation.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
groovy-implicit-return.mdc
---
description:
globs: **/*.groovy
alwaysApply: false
---

# Groovy Implicit Return

Groovy supports implicit returns (the last expression in a method is the return value). Do **not** flag or suggest adding explicit `return` statements to Groovy methods.

## Rules

- Never warn about or add `return` keywords to satisfy a "missing explicit return" linter hint in Groovy code.
- The last evaluated expression in a Groovy method is implicitly returned — this is valid, idiomatic Groovy.
- Do not treat the absence of a `return` keyword as a bug or style violation.

## Example

```groovy
// ✅ correct — implicit return is idiomatic Groovy
List searchWithAQL( Map map ) {
  // ...
  readJSON( returnPojo: true, text: someText )?.results?.collect { it.path + '/' + it.name } ?: []
}

// ❌ unnecessary — do not add explicit return
List searchWithAQL( Map map ) {
  // ...
  return readJSON( returnPojo: true, text: someText )?.results?.collect { it.path + '/' + it.name } ?: []
}
```

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.