agentleFS
NetcrackerNetcracker/qubership-ai-agent-telemetry/.cursor/rules/qubership-workflow-hub-usage.mdc

qubership-ai-agent-telemetry / rules

Cursor rule1 starsChanged 25 days agoApache-2.0View on GitHub

Triggers for qubership-workflow-hub-usage skills when working on GitHub Actions workflows.

The file

We split this qubership-workflow-hub-usage.mdc into the rules it gives an agent

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

  • 3

    Very specific

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

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

    When designing, writing, reviewing, or debugging .github/workflows/*.yml files that consume netcracker/qubership-workflow-hub actions or …

    line 8
  2. Very specific:

    When a workflow step needs a specific Qubership action (Docker build/push, version/tag rendering, Maven/npm/Python publishing, package …

    line 12
  3. Very specific:

    When the user asks for a CI/CD workflow that may already exist as a curated Netcracker template (Docker build/release, Maven/npm/Python …

    line 17

≈ “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
qubership-workflow-hub-usage.mdc
---
description: Triggers for qubership-workflow-hub-usage skills when working on GitHub Actions workflows.
globs: **/.github/workflows/*.{yml,yaml}
---

# Qubership Workflow Hub Usage

When designing, writing, reviewing, or debugging `.github/workflows/*.yml` files
that consume `netcracker/qubership-workflow-hub` actions or `Netcracker/.github` templates,
apply the `qubership-workflow-conventions` skill.

When a workflow step needs a specific Qubership action (Docker build/push,
version/tag rendering, Maven/npm/Python publishing, package cleanup, Helm charts,
security scans, email notifications, etc.) and you need to find the right action or read its README,
apply the `qubership-actions-guide` skill.

When the user asks for a CI/CD workflow that may already exist as a curated
Netcracker template (Docker build/release, Maven/npm/Python release, Helm chart
release, security scan, SBOM, PR hygiene, license/lint, GHCR cleanup),
apply the `qubership-templates-guide` skill.

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.