qubership-ai-packages

Prepare a pull request that adds Qubership baseline agent support to a repository: install qubership-essentials, run apm install for repository-declared harnesses, commit generated agent assets, and configure generated-file attributes and Super-Linter exclusions.

Author an Architecture Decision Record. Use whenever the user wants to capture, write, or draft an architecture or system-design decision — "write an ADR", "document this decision", "add a decision record", "we decided to use X, record it" — even when they don't say "ADR" but describe a choice worth tracking (a pattern, a non-functional requirement, a dependency, an interface, or a tool selection). Also use to supersede or amend an existing ADR.

British-English-first style guidance for developer-facing text of any length — README and docs, code comments and docstrings, Javadoc / KDoc / TSDoc / JSDoc, commit messages, PR descriptions and review replies, design docs, changelog entries, UI strings (buttons, labels, placeholders, tooltips), error and log messages, and English-side localisation files (.po, .properties, JSON i18n). Use whenever the task involves English developer text — writing, editing, rewriting, translating, localising, reviewing, proofreading, verifying, auditing, double-checking, or cross-checking. Length does not matter: a one-line `msgstr`, a `// FIXME` comment, or a three-word button label is in scope. Also covers choice of English identifier names (methods, variables, classes, files, tests) read by humans. Covers em-dash usage, hyphen stacking, sentence structure, that/which, gerunds after rather than, hedging, inclusive language, and British/American dialect consistency. Do not use for casual chat replies to the user.

Triage failing checks on dependency-update PRs (Renovate or Dependabot) and drive them back to green: classify each failure, fix the clear ones, ask about the rest. Use only when the user asks to triage, fix, or sweep failing checks on dependency-update PRs — pass a PR number for one PR, or none to process every open dependency-update PR with a failing check.

Set up Renovate so dependency-update PRs merge themselves once CI passes. Use when enabling automerge in renovate.json, deciding which GitHub status checks to mark as required so a green PR means the tests actually ran, or adding a CI-gate job that folds several test jobs into one required check.

French technical-prose conventions for software documentation, README files, UI strings, error messages, logs, code comments, PR descriptions, changelog entries, and French localization. Use when writing, editing, translating, or reviewing French software-facing prose. Defaults to fr-FR, supports fr-CA mode, and focuses on clear natural French, technical precision, terminology consistency, and avoiding over-translated or LLM-like phrasing.

Russian style guidance for developer-facing text of any length — README and docs, code comments, docstrings, commit messages, PR descriptions, changelog entries, UI strings (buttons, labels, placeholders, tooltips), error and log messages, and localisation files (.po, .properties, JSON i18n). Use whenever the task involves Russian developer text — writing, editing, rewriting, translating, localising, reviewing, proofreading, verifying, auditing, double-checking, sanity-checking, cross-checking. Trigger verbs include the Russian "напиши", "переведи", "локализуй", "проверь", "перепроверь", "сверь", "отревью". Length does not matter: a one-line `msgstr` is in scope. Focuses on clear natural Russian, technical precision, terminology consistency, and avoiding bureaucratic or LLM-like phrasing.