agentleFS
sagar-shirwalkarsagar-shirwalkar/servicenow-atlas/.agents/skills/atlas-ci-release/SKILL.md

atlas-ci-release

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Manage CI bundle releases: manual dispatch, tag naming, monitoring the build-bundle workflow, promoting a release, and rolling back. Use when releasing a new bundle, debugging a CI failure, or rolling back to a previous bundle.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT dispatch from main if there are unmerged changes that affect the bundle content.

    line 35
  2. Distinctive:

    If the workflow exceeds 60 minutes, check the runner logs for:

    line 64
  3. Distinctive:

    When the build workflow succeeds:

    line 71
  4. Distinctive:

    No code rollback is needed — bundles are independent artifacts.

    line 95

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

When to use

  • User asks to "release a new bundle", "trigger a CI build", "create a release"
  • User wants to "tag a release", "cut a release"
  • A CI build failed and needs investigation
  • User wants to "roll back to the previous bundle"

Not for

  • Building the bundle locally (use atlas-build-bundle)
  • Changing the CI workflow itself (edit .github/workflows/build-bundle.yml manually)

Workflow

1. Manual dispatch

Go to GitHub → Actions → Build Bundle → Run workflow.

Parameters:

ParameterValueWhen
model_idXenova/bge-small-en-v1.5Default — production builds
refmainStable releases
ref<branch>Testing a feature branch

Do NOT dispatch from main if there are unmerged changes that affect the bundle content.

2. Tag naming convention

Tags are auto-generated from the workflow run: bundle-<YYYYMMDD>-<run_number> (e.g., bundle-20260622-42).

For manual tags (when the auto-tag is insufficient):

git tag bundle-<YYYYMMDD>-<run_number>-<reason>
git push origin bundle-<YYYYMMDD>-<run_number>-<reason>

Reasons: hotfix, rollback, rc1, rc2.

3. Monitor the workflow

The workflow takes ~30–60 minutes.

PhaseDurationKey log lines
Setup1 minSetup uv, Cache npm
Clone docs2–3 minCloning servicenow-docs
Chunk2–5 minChunked N files
Download model1–3 minDownloading Xenova/bge-small-en-v1.5
Embed15–30 minEmbedding chunk N/M
Package1 minCreating tarball
Smoke test2 minSmoke test passed
Publish1 minUploading release asset

If the workflow exceeds 60 minutes, check the runner logs for:

  • Slow model download (HF mirror issues)
  • OOM (runner has 2 vCPUs / 7 GB)
  • Stuck chunking (infinite loop in a single file)

4. Promote a release

When the build workflow succeeds:

  1. The tarball is uploaded as a GitHub Release asset.
  2. The release name matches the tag.
  3. To make it the "latest" release:
    gh release edit <tag> --latest

5. Roll back

To revert to a previous bundle:

# Find the previous release's tag
gh release list --limit 10

# Download the previous bundle
gh release download <previous-tag> --pattern '*.tar.zst'

# Make it the latest
gh release edit <previous-tag> --latest

No code rollback is needed — bundles are independent artifacts. Just re-point consumers.

CI workflow reference

File: .github/workflows/build-bundle.yml

Key detailValue
TriggerMonthly cron (0 6 1 * *) + workflow_dispatch
Runnerubuntu-latest (2 vCPU, 7 GB, no GPU)
ModelXenova/bge-small-en-v1.5 (int8, 384-dim)
BackendONNX+CPU (forced via --backend onnx-cpu)
Batch size256
EnvHF_TOKEN set from secrets
Post-buildatlas-smoke
ArtifactGitHub Release (auto-tag)

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.