How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

lint - Prompt - OpenSmartRoute

Name: lint
Author: Netcracker

Prompt file imported from Netcracker/qubership-nifi-registry (.cursor/commands/lint.md). Fill in {{arguments}} before use. Copyright stays with the author.

Lint the module {{arguments}} with the project's five linters, then fix every finding in the source.

If {{arguments}} is empty, ask which module to lint (a directory path relative to the repository root, e.g. qubership-nifi-common) and stop until the user answers.

Treat {{arguments}} as a module directory path relative to the repository root. Run every command from the repository root so the linter configs' relative paths resolve. codespell, checkstyle, markdownlint, and textlint reuse the configs under .github/linters/; editorconfig-checker reads the formatting rules from the root .editorconfig and runs with default settings (the repository has no .editorconfig-checker.json). These are the same rules CI enforces.

Every command excludes Maven build output (target/), test fixtures (*/test/resources/*), and APM agent content (skills/rules/commands under .claude/.cursor/.agents), mirroring the FILTER_REGEX_EXCLUDE filter in .github/super-linter.env.

1. Validate the module

Confirm the directory {{arguments}} exists. If not, report it and stop.
Check whether {{arguments}}/pom.xml exists. If it does not, skip checkstyle (step 4) with a note: the module is not a Maven project.

2. codespell: every text file in the module

codespell --config .github/linters/.codespellrc \
  --skip "*/target/*,*/test/resources/*,*/.claude/skills/*,*/.claude/rules/*,*/.claude/commands/*,*/.cursor/skills/*,*/.cursor/rules/*,*/.cursor/commands/*,*/.agents/skills/*,*/.agents/rules/*,*/.agents/commands/*" \
  {{arguments}}

--skip excludes Maven build output, test fixtures, and APM agent content. If codespell is not on PATH, print a one-line note and skip this step (do not fail).

3. markdownlint: `.md` files in the module

markdownlint-cli2 --config .github/linters/.markdownlint.json "{{arguments}}/**/*.md" \
  "!**/target/**" "!**/test/resources/**" "!**/.{claude,cursor,agents}/{skills,rules,commands}/**"

The negation globs exclude Maven build output, test fixtures, and APM agent content. Use forward slashes in the path: the CLI globs this argument, and a backslash path matches nothing on Windows. Prefer markdownlint-cli2; fall back to markdownlint (markdownlint-cli) if only that is installed, using its --ignore flag for the exclusions:

markdownlint --config .github/linters/.markdownlint.json \
  --ignore "**/target/**" --ignore "**/test/resources/**" \
  --ignore "**/.claude/{skills,rules,commands}/**" \
  --ignore "**/.cursor/{skills,rules,commands}/**" \
  --ignore "**/.agents/{skills,rules,commands}/**" \
  "{{arguments}}/**/*.md"

If neither CLI is on PATH, print a note and skip.

4. checkstyle: `.java` files in the module, via Maven

mvn -q -pl {{arguments}} checkstyle:check -Dcheckstyle.failOnViolation=false

failOnViolation=false lets Maven list every violation in one pass instead of aborting on the first. Read the full structured list from {{arguments}}/target/checkstyle-result.xml. If mvn is not on PATH, print a note and skip.

5. editorconfig-checker: every text file in the module

editorconfig-checker -exclude 'target/|/test/resources/|/\.(cursor|claude|agents)/(skills|rules|commands)/' {{arguments}}

editorconfig-checker reads the formatting rules from the root .editorconfig. With no -config flag it runs with default tool settings -- the repository has no .editorconfig-checker.json -- the same as CI. -exclude adds the build-output, test-fixture, and APM agent content filters on top of the tool's built-in excludes. If editorconfig-checker is not on PATH, print a one-line note and skip this step (do not fail).

6. textlint: `.md` and `.txt` files in the module

npx textlint -f unix --config .github/linters/.textlintrc \
  "{{arguments}}/**/*.md" "{{arguments}}/**/*.txt"

textlint reuses .github/linters/.textlintrc (the terminology rule, e.g. id -> ID, github -> GitHub), the same config CI's super-linter uses. Prefer the repository's local CLI (node_modules/.bin/textlint) via npx textlint; if textlint is not installed, print a one-line note and skip this step (do not fail).

If the module has no .md or .txt files, textlint exits non-zero with Not found target files -- treat that as "nothing to lint" and move on, it is not a failure.

textlint does not support !-negation in CLI glob arguments; it reads exclusions from a .textlintignore file (pass one with --ignore-path if needed). If a finding lands in build output (target/), a test fixture (*/test/resources/*), or APM agent content (skills/rules/commands under .claude/.cursor/.agents), ignore it -- CI does not lint those paths.

7. Fix every finding by hand

Use Read and Edit, not auto-fixers (no codespell --write-changes, no markdownlint --fix, no textlint --fix). Fix the source, not the rules.

codespell: correct the flagged spelling in the source.
markdownlint: fix per the rule ID (line length, list indent, heading spacing, and so on).
checkstyle: fix per the violation (Javadoc, imports, naming, whitespace, and so on).
editorconfig-checker: fix per the .editorconfig rule (charset, final newline, trailing whitespace, indent style, and so on).
textlint: correct the flagged term in the source per the suggested replacement (e.g. id -> ID).

Never modify the linter configs to silence a finding, leave .codespellrc, .markdownlint.json, sun_checks.xml, suppressions.xml, .textlintrc, and .editorconfig untouched.

If a finding looks legitimate or deliberate, such as a real domain term codespell flags, or a checkstyle violation that is an intentional exception, do not silence it in a config and do not force an unwanted source change. Leave it as is and report it to the user with the file, line, and why it appears intentional, so they can decide.

8. Re-run and confirm clean

Re-run each linter that reported issues. Repeat the fix/re-run loop until no findings remain, except for any you have deliberately left for the user to decide.

9. Summarize

Report, per linter:

issues found and issues fixed;
anything skipped because its tool is missing;
any findings left for the user to decide, each with file, line, and reason.

Configs are never modified by this command.

Install lint and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Lint the module `{{arguments}}` with the project's five linters, then fix every finding in the source. If `{{arguments}}` is empty, ask which module to lint (a directory path relative to the repository root, e.g. `qubership-nifi-common`) and stop until the user answers. Treat `{{arguments}}` as a module directory path relative to the repository root. Run every command **from the repository root** so the linter configs' relative paths resolve. codespell, checkstyle, markdownlint, and textlint reuse the configs under `.github/linters/`; editorconfig-checker reads the formatting rules from the root `.editorconfig` and runs with default settings (the repository has no `.editorconfig-checker.json`). These are the same rules CI enforces. Every command excludes Maven build output (`target/`), test fixtures (`*/test/resources/*`), and APM agent content (`skills`/`rules`/`commands` under `.claude`/`.cursor`/`.agents`), mirroring the `FILTER_REGEX_EXCLUDE` filter in `.github/super-linter.env`. ## 1. Validate the module - Confirm the directory `{{arguments}}` exists. If not, report it and stop. - Check whether `{{arguments}}/pom.xml` exists. If it does not, skip checkstyle (step 4) with a note: the module is not a Maven project. ## 2. codespell: every text file in the module ```bash codespell --config .github/linters/.codespellrc \ --skip "*/target/*,*/test/resources/*,*/.claude/skills/*,*/.claude/rules/*,*/.claude/commands/*,*/.cursor/skills/*,*/.cursor/rules/*,*/.cursor/commands/*,*/.agents/skills/*,*/.agents/rules/*,*/.agents/commands/*" \ {{arguments}} ``` `--skip` excludes Maven build output, test fixtures, and APM agent content. If `codespell` is not on `PATH`, print a one-line note and skip this step (do not fail). ## 3. markdownlint: `.md` files in the module ```bash markdownlint-cli2 --config .github/linters/.markdownlint.json "{{arguments}}/**/*.md" \ "!**/target/**" "!**/test/resources/**" "!**/.{claude,cursor,agents}/{skills,rules,commands}/**" ``` The negation globs exclude Maven build output, test fixtures, and APM agent content. Use forward slashes in the path: the CLI globs this argument, and a backslash path matches nothing on Windows. Prefer `markdownlint-cli2`; fall back to `markdownlint` (markdownlint-cli) if only that is installed, using its `--ignore` flag for the exclusions: ```bash markdownlint --config .github/linters/.markdownlint.json \ --ignore "**/target/**" --ignore "**/test/resources/**" \ --ignore "**/.claude/{skills,rules,commands}/**" \ --ignore "**/.cursor/{skills,rules,commands}/**" \ --ignore "**/.agents/{skills,rules,commands}/**" \ "{{arguments}}/**/*.md" ``` If neither CLI is on `PATH`, print a note and skip. ## 4. checkstyle: `.java` files in the module, via Maven ```bash mvn -q -pl {{arguments}} checkstyle:check -Dcheckstyle.failOnViolation=false ``` `failOnViolation=false` lets Maven list every violation in one pass instead of aborting on the first. Read the full structured list from `{{arguments}}/target/checkstyle-result.xml`. If `mvn` is not on `PATH`, print a note and skip. ## 5. editorconfig-checker: every text file in the module ```bash editorconfig-checker -exclude 'target/|/test/resources/|/\.(cursor|claude|agents)/(skills|rules|commands)/' {{arguments}} ``` editorconfig-checker reads the formatting rules from the root `.editorconfig`. With no `-config` flag it runs with default tool settings -- the repository has no `.editorconfig-checker.json` -- the same as CI. `-exclude` adds the build-output, test-fixture, and APM agent content filters on top of the tool's built-in excludes. If `editorconfig-checker` is not on `PATH`, print a one-line note and skip this step (do not fail). ## 6. textlint: `.md` and `.txt` files in the module ```bash npx textlint -f unix --config .github/linters/.textlintrc \ "{{arguments}}/**/*.md" "{{arguments}}/**/*.txt" ``` textlint reuses `.github/linters/.textlintrc` (the `terminology` rule, e.g. `id` -> `ID`, `github` -> `GitHub`), the same config CI's super-linter uses. Prefer the repository's local CLI (`node_modules/.bin/textlint`) via `npx textlint`; if textlint is not installed, print a one-line note and skip this step (do not fail). If the module has no `.md` or `.txt` files, textlint exits non-zero with `Not found target files` -- treat that as "nothing to lint" and move on, it is not a failure. textlint does **not** support `!`-negation in CLI glob arguments; it reads exclusions from a `.textlintignore` file (pass one with `--ignore-path` if needed). If a finding lands in build output (`target/`), a test fixture (`*/test/resources/*`), or APM agent content (`skills`/`rules`/`commands` under `.claude`/`.cursor`/`.agents`), ignore it -- CI does not lint those paths. ## 7. Fix every finding by hand Use `Read` and `Edit`, not auto-fixers (no `codespell --write-changes`, no `markdownlint --fix`, no `textlint --fix`). Fix the source, not the rules. - **codespell**: correct the flagged spelling in the source. - **markdownlint**: fix per the rule ID (line length, list indent, heading spacing, and so on). - **checkstyle**: fix per the violation (Javadoc, imports, naming, whitespace, and so on). - **editorconfig-checker**: fix per the `.editorconfig` rule (charset, final newline, trailing whitespace, indent style, and so on). - **textlint**: correct the flagged term in the source per the suggested replacement (e.g. `id` -> `ID`). **Never modify the linter configs** to silence a finding, leave `.codespellrc`, `.markdownlint.json`, `sun_checks.xml`, `suppressions.xml`, `.textlintrc`, and `.editorconfig` untouched. If a finding looks legitimate or deliberate, such as a real domain term codespell flags, or a checkstyle violation that is an intentional exception, do not silence it in a config and do not force an unwanted source change. Leave it as is and report it to the user with the file, line, and why it appears intentional, so they can decide. ## 8. Re-run and confirm clean Re-run each linter that reported issues. Repeat the fix/re-run loop until no findings remain, except for any you have deliberately left for the user to decide. ## 9. Summarize Report, per linter: - issues found and issues fixed; - anything skipped because its tool is missing; - any findings left for the user to decide, each with file, line, and reason. Configs are never modified by this command.

{ "prompt": "Lint the module `{{arguments}}` with the project's five linters, then fix every finding\nin the source.\n\nIf `{{arguments}}` is empty, ask which module to lint (a directory path relative to the\nrepository root, e.g. `qubership-nifi-common`) and stop until the user answers.\n\nTreat `{{arguments}}` as a module directory path relative to the repository root. Run every\ncommand **from the repository root** so the linter configs' relative paths resolve.\ncodespell, checkstyle, markdownlint, and textlint reuse the configs under `.github/linters/`;\neditorconfig-checker reads the formatting rules from the root `.editorconfig` and runs\nwith default settings (the repository has no `.editorconfig-checker.json`). These are the same\nrules CI enforces.\n\nEvery command excludes Maven build output (`target/`), test fixtures\n(`*/test/resources/*`), and APM agent content (`skills`/`rules`/`commands` under\n`.claude`/`.cursor`/`.agents`), mirroring the `FILTER_REGEX_EXCLUDE` filter in\n`.github/super-linter.env`.\n\n## 1. Validate the module\n\n- Confirm the directory `{{arguments}}` exists. If not, report it and stop.\n- Check whether `{{arguments}}/pom.xml` exists. If it does not, skip checkstyle (step 4)\n with a note: the module is not a Maven project.\n\n## 2. codespell: every text file in the module\n\n```bash\ncodespell --config .github/linters/.codespellrc \\\n --skip \"*/target/*,*/test/resources/*,*/.claude/skills/*,*/.claude/rules/*,*/.claude/commands/*,*/.cursor/skills/*,*/.cursor/rules/*,*/.cursor/commands/*,*/.agents/skills/*,*/.agents/rules/*,*/.agents/commands/*\" \\\n {{arguments}}\n```\n\n`--skip` excludes Maven build output, test fixtures, and APM agent content. If\n`codespell` is not on `PATH`, print a one-line note and skip this step (do not fail).\n\n## 3. markdownlint: `.md` files in the module\n\n```bash\nmarkdownlint-cli2 --config .github/linters/.markdownlint.json \"{{arguments}}/**/*.md\" \\\n \"!**/target/**\" \"!**/test/resources/**\" \"!**/.{claude,cursor,agents}/{skills,rules,commands}/**\"\n```\n\nThe negation globs exclude Maven build output, test fixtures, and APM agent content. Use\nforward slashes in the path: the CLI globs this argument, and a backslash path matches\nnothing on Windows. Prefer `markdownlint-cli2`; fall back to `markdownlint`\n(markdownlint-cli) if only that is installed, using its `--ignore` flag for the exclusions:\n\n```bash\nmarkdownlint --config .github/linters/.markdownlint.json \\\n --ignore \"**/target/**\" --ignore \"**/test/resources/**\" \\\n --ignore \"**/.claude/{skills,rules,commands}/**\" \\\n --ignore \"**/.cursor/{skills,rules,commands}/**\" \\\n --ignore \"**/.agents/{skills,rules,commands}/**\" \\\n \"{{arguments}}/**/*.md\"\n```\n\nIf neither CLI is on `PATH`, print a note and skip.\n\n## 4. checkstyle: `.java` files in the module, via Maven\n\n```bash\nmvn -q -pl {{arguments}} checkstyle:check -Dcheckstyle.failOnViolation=false\n```\n\n`failOnViolation=false` lets Maven list every violation in one pass instead of aborting\non the first. Read the full structured list from `{{arguments}}/target/checkstyle-result.xml`.\nIf `mvn` is not on `PATH`, print a note and skip.\n\n## 5. editorconfig-checker: every text file in the module\n\n```bash\neditorconfig-checker -exclude 'target/|/test/resources/|/\\.(cursor|claude|agents)/(skills|rules|commands)/' {{arguments}}\n```\n\neditorconfig-checker reads the formatting rules from the root `.editorconfig`. With no\n`-config` flag it runs with default tool settings -- the repository has no\n`.editorconfig-checker.json` -- the same as CI. `-exclude` adds the build-output,\ntest-fixture, and APM agent content filters on top of the tool's built-in excludes. If\n`editorconfig-checker` is not on `PATH`, print a one-line note and skip this step (do not\nfail).\n\n## 6. textlint: `.md` and `.txt` files in the module\n\n```bash\nnpx textlint -f unix --config .github/linters/.textlintrc \\\n \"{{arguments}}/**/*.md\" \"{{arguments}}/**/*.txt\"\n```\n\ntextlint reuses `.github/linters/.textlintrc` (the `terminology` rule, e.g. `id` -> `ID`,\n`github` -> `GitHub`), the same config CI's super-linter uses. Prefer the repository's local\nCLI (`node_modules/.bin/textlint`) via `npx textlint`; if textlint is not installed, print a\none-line note and skip this step (do not fail).\n\nIf the module has no `.md` or `.txt` files, textlint exits non-zero with\n`Not found target files` -- treat that as \"nothing to lint\" and move on, it is not a\nfailure.\n\ntextlint does **not** support `!`-negation in CLI glob arguments; it reads exclusions from a\n`.textlintignore` file (pass one with `--ignore-path` if needed). If a finding lands in build\noutput (`target/`), a test fixture (`*/test/resources/*`), or APM agent content\n(`skills`/`rules`/`commands` under `.claude`/`.cursor`/`.agents`), ignore it -- CI does not\nlint those paths.\n\n## 7. Fix every finding by hand\n\nUse `Read` and `Edit`, not auto-fixers (no `codespell --write-changes`, no\n`markdownlint --fix`, no `textlint --fix`). Fix the source, not the rules.\n\n- **codespell**: correct the flagged spelling in the source.\n- **markdownlint**: fix per the rule ID (line length, list indent, heading spacing, and\n so on).\n- **checkstyle**: fix per the violation (Javadoc, imports, naming, whitespace, and so\n on).\n- **editorconfig-checker**: fix per the `.editorconfig` rule (charset, final newline,\n trailing whitespace, indent style, and so on).\n- **textlint**: correct the flagged term in the source per the suggested replacement (e.g.\n `id` -> `ID`).\n\n**Never modify the linter configs** to silence a finding, leave `.codespellrc`,\n`.markdownlint.json`, `sun_checks.xml`, `suppressions.xml`, `.textlintrc`, and `.editorconfig`\nuntouched.\n\nIf a finding looks legitimate or deliberate, such as a real domain term codespell flags,\nor a checkstyle violation that is an intentional exception, do not silence it in a config and\ndo not force an unwanted source change. Leave it as is and report it to the user with the\nfile, line, and why it appears intentional, so they can decide.\n\n## 8. Re-run and confirm clean\n\nRe-run each linter that reported issues. Repeat the fix/re-run loop until no findings\nremain, except for any you have deliberately left for the user to decide.\n\n## 9. Summarize\n\nReport, per linter:\n\n- issues found and issues fixed;\n- anything skipped because its tool is missing;\n- any findings left for the user to decide, each with file, line, and reason.\n\nConfigs are never modified by this command.", "variables": [ "arguments" ], "notes": "Run codespell, checkstyle, markdownlint, editorconfig-checker and textlint on a module and fix the findings. Tools: Bash, Read, Edit, Grep, Glob. Arguments: <module-path>.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/Netcracker/qubership-nifi-registry", "path": ".cursor/commands/lint.md", "ref": "4a74ae64df5910fa958a0f582c1b673bb0f15313", "url": "https://github.com/Netcracker/qubership-nifi-registry/blob/4a74ae64df5910fa958a0f582c1b673bb0f15313/.cursor/commands/lint.md", "key": "Netcracker/qubership-nifi-registry/.cursor/commands/lint.md" } } }

lint

About

1. Validate the module

2. codespell: every text file in the module

3. markdownlint: `.md` files in the module

4. checkstyle: `.java` files in the module, via Maven

5. editorconfig-checker: every text file in the module

6. textlint: `.md` and `.txt` files in the module

7. Fix every finding by hand

8. Re-run and confirm clean

9. Summarize

Install lint and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

About

1. Validate the module

2. codespell: every text file in the module

3. markdownlint: .md files in the module

4. checkstyle: .java files in the module, via Maven

5. editorconfig-checker: every text file in the module

6. textlint: .md and .txt files in the module

7. Fix every finding by hand

8. Re-run and confirm clean

9. Summarize

Install lint and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews

3. markdownlint: `.md` files in the module

4. checkstyle: `.java` files in the module, via Maven

6. textlint: `.md` and `.txt` files in the module