agentleFS
NetcrackerNetcracker/qubership-ai-agent-telemetry/.claude/skills/qubership-templates-guide/SKILL.md

qubership-templates-guide

Skill1 starsChanged 29 days agoApache-2.0View on GitHub

Navigation-only skill for the Netcracker workflow-templates catalog at Netcracker/.github/workflow-templates. Use when the user asks for a CI/CD workflow that may already exist as a curated template (Docker build/release, Maven/npm/Python release, Helm chart release, security scan, SBOM, PR hygiene, license/lint, GHCR cleanup). Points to the canonical template files and explains how to fork. All rules (pinning, permissions, anti-hallucination, naming) live in qubership-workflow-conventions — this skill does not restate them.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If a matching template is found → tell the user which template, fetch it, use it as the base.

    line 19
  2. Very specific:

    If no match → return to qubership-workflow-conventions Workflow design process Step 2 and build from scratch.

    line 20
  3. Distinctive:

    If the file returns 404 — inform the user, show the current list, and pick the nearest alternative or fall back to building from scratch.

    line 32
  4. Very specific:

    Use a commit SHA or a tag for <ref> in production.

    line 45
  5. Very specific:

    Read the paired .properties.json: when present (same basename, .properties.json extension).

    line 48
  6. Distinctive:

    When forking a template into a user's repo:

    line 139

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
SKILL.md

qubership-templates-guide

Navigator for the official Netcracker workflow-templates catalog at Netcracker/.github/workflow-templates.

These templates are the canonical, production-tested workflows used across the org. The catalog is the source of truth — this skill helps you locate the right template and adapt it.

How to use

Run this step when creating a new workflow or restructuring an existing one (changing jobs, triggers, or pipeline shape). Skip for small targeted edits (timeout, branch filter, input value).

If a matching template is found → tell the user which template, fetch it, use it as the base. If no match → return to qubership-workflow-conventions Workflow design process Step 2 and build from scratch.

  1. Read the user's task. Identify the CI/CD operation (release, build, scan, lint, cleanup, etc.).
  2. Match against the catalog table below. Pick the closest template by purpose, not by name resemblance. Then verify it still exists before using it:

    gh api repos/Netcracker/.github/contents/workflow-templates/<file> --jq '.name'

    If the file returns 404 — inform the user, show the current list, and pick the nearest alternative or fall back to building from scratch.

  3. Fetch the template ONCE. Two equivalent ways:

    gh api repos/Netcracker/.github/contents/workflow-templates/<file> --jq '.content' | base64 -d
    WebFetch → https://raw.githubusercontent.com/Netcracker/.github/main/workflow-templates/<file>

    Use a commit SHA or a tag for <ref> in production; main is acceptable for exploration.

  4. Read the paired .properties.json when present (same basename, .properties.json extension). It contains the GitHub UI metadata — description, categories, filePatterns — useful for confirming the template's intent.
  5. Adapt the template. See What to adapt vs. keep below.
  6. Apply qubership-workflow-conventions (Mandatory conventions) to every adapted line. Replace template SHAs with values from the Pin table in qubership-actions-guide.
  7. Tell the user which template you started from, including the raw URL or repo path, so they can compare and re-fetch updates.

Catalog: task → template

The table below is a snapshot for fast lookup; verify the file exists in the current Netcracker/.github/workflow-templates directory before using it (templates are added, renamed, and removed):

gh api repos/Netcracker/.github/contents/workflow-templates --jq '.[].name'

Docker (CI builds)

TaskTemplateTriggerKey details
Single Docker image, no config filedev-docker-build-single-image.ymlpush + pull_request + workflow_dispatchmetadata-action → docker-action; inline image name; dry-run input
Multiple Docker images from .qubership/docker.cfgdev-docker-build-multiple-images.ymlpush + pull_request + workflow_dispatchdocker-config-resolver → metadata-action → docker-action (matrix); dry-run input
Build only changed images (changeset detection)dev-docker-build-selective.ymlpush + pull_request + workflow_dispatchlike multiple-images but filters components by changed files via tj-actions/changed-files
Build Maven project then Docker imagedev-mvn-docker-build.ymlpush + pull_request + workflow_dispatchMaven build → upload-artifact → docker-action with download-artifact

Releases

TaskTemplateTriggerKey details
Release Docker images + GitHub releasedocker-release.yamlworkflow_dispatchcheck-tag → docker-config-resolver (.qubership/docker.cfg) → create-tag → docker-action (matrix) → release-drafter
Release Maven artifact (Central or GH Packages)maven-release-v2.yamlworkflow_dispatchdry-run-build → deploy (maven-release) → docker-build (optional) → github-release; needs GPG secrets + GH App token for protected branch
Deploy Maven SNAPSHOTmaven-snapshot-deploy.yamlworkflow_dispatchmaven-snapshot-deploy action; no tag/release created
Release npm packagenpm-release.yamlworkflow_dispatchnpm publish to npmjs or GitHub Packages
Publish npm package (lightweight)npm-publish.yamlworkflow_dispatchlightweight npm publish, no release drafter
Release Python package via Poetrypython-release.yamlworkflow_dispatchpoetry-publisher → PyPI; dry-run support
Release Helm charts + Docker imageshelm-charts-release.yamlworkflow_dispatchcheck-tag → docker dry-run → charts-values-update-action → docker-action (matrix) → release-drafter + assets-action (.tgz); needs .qubership/helm-charts-release-config.yaml + .qubership/docker-build-config.cfg

Security and supply chain

TaskTemplateTriggerKey details
Security scan via docker.cfg configsecurity-scan-with-config.ymlworkflow_dispatch + schedule (Sunday)docker-config-resolver → filter security_scan==true → re-security-scan (matrix); supports manual overrides per-input
Security scan — discover from GHCRsecurity-scan.ymlworkflow_dispatch + schedule (Sunday)ghcr-discover-repo-packages → re-security-scan (matrix); no config file needed
Security scan for APIHUBsecurity-scan-apihub.ymlworkflow_dispatch + scheduleAPIHUB-specific variant
CVE scan via Docker Scoutscout-cves.ymlworkflow_dispatch + scheduleDocker Scout instead of Trivy/Grype
Generate SBOM and attach to releasesbom-to-release.yamlworkflow_dispatchcdxgen → attach to GitHub release
Native GitHub dependency review on PRdependency-review.yamlpull_requestGitHub native dependency-review action
OSSF Scorecardossf-scorecard.yamlschedule + push to mainOSSF scorecard upload

Code quality and linting

TaskTemplate
Lint and test Helm chartslint-test-chart.yaml
Lint markdown / source via super-lintersuper-linter.yaml
Check third-party licensescheck-license.yaml
Add license headers to source fileslicense-header.yml
Check broken linkslink-checker.yaml
Lint Renovate configrenovate-config-lint.yaml
Profanity filter for issues/PRsprofanity-filter.yaml

PR hygiene

TaskTemplate
Conventional Commits PR checkpr-conventional-commits.yaml
Lint PR titlepr-lint-title.yaml
Auto-label PRsautomatic-pr-labeler.yaml
Auto-assign reviewerspr-assigner.yml
Auto-assign issues to project boardauto-assign-project-to-issue.yml
CLA assistantcla.yaml

Build and maintenance

TaskTemplate
Build Go projectgo-build.yaml
Cleanup old container versions in GHCRcleanup-old-docker-container.yaml
Bump test workflow versionsbump-test-workflows-version.yaml

What to adapt vs. keep

When forking a template into a user's repo:

Adapt (safe, expected):

  • Workflow name: and run-name: for repo-specific labels.
  • Image names, package names, registry URLs that are repo-specific.
  • Secret names if the user's repo uses different conventions.
  • Path filters in paths-ignore: to match repo layout.
  • inputs: defaults (versions, tags) for repo-specific norms.
  • Trigger filters (branches, tags) for the repo's branching model.

Keep (do not "improve" without a reason):

  • Job-level permissions: blocks — the templates already follow least-privilege.
  • Job structure and needs: order — typical templates implement dry-run → deploy → release stages for a reason.
  • Config-file references (.qubership/docker.cfg, etc.) — these are the org-standard locations.

Always tell the user about:

  • Required secrets the template uses (e.g. GH_BUMP_VERSION_APP_ID, MAVEN_GPG_PRIVATE_KEY, PYPI_API_TOKEN).
  • Required config files (.qubership/docker.cfg, .qubership/helm-charts-release-config.yaml, .github/release-drafter-config.yml) and where to find examples.
  • Required org/repo variables (vars.GH_BUMP_VERSION_APP_ID etc.).

What this skill does NOT do

  • It does not generate workflows from scratch — for that, follow qubership-workflow-conventions.
  • It does not duplicate template content — templates are fetched on demand from the catalog.
  • It does not cover reusable workflows (re-*.yml) — those are not part of the workflow-templates catalog.

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.