Migrate a repository from Bitbucket+Jenkins to GitHub+GitHub Actions, including git history, branches, tags, CI/CD pipeline conversion (Jenkinsfile → ci-cd.yml), helm chart updates, branch deletion ruleset, and post-migration validation. Asks clarifying questions and handles external dependencies interactively. Use when migrating UNCTAD-eRegistrations repos from Bitbucket to GitHub.
EnglishConvert Docker Compose files to Docker Swarm stack format for eRegistrations deployments. Handles env var replacement, secrets management, init-swarm.sh generation, reference stack validation, and dry-run preview. Use when migrating docker-compose.yml to docker-stack.yml, adding deploy sections, configuring overlay networks, or converting environment secrets to Docker Swarm secrets.
EnglishGenerate a citizen-facing HTML user manual for ONE specific eRegistrations service. Use when the user provides a service ID or BPA URL, asks to "document a service", "create a manual for [service name]", "generate user guide for [service]", "manual for service [name]", or "manual for [service] in [instance]". Do NOT use when the user wants ALL services documented (use /service-manual-all) or wants a technical Excel analysis (use /eregistrations-docs).
EnglishUpgrade a single eRegistrations instance under Conf- /compose/ /docker-stack.yml from 2.13 to 2.14, where is one of dev/test/preview/prelive/live. This is the largest mechanical step in the chain: bumps every unctad/ :$ VER (or pinned semver) image to :RC (the platform tag introduced in 2.14), drops the legacy Keycloak /auth path from internal and public URLs across bpa-frontend, bpa-backend, camunda, mule, ereg-cms-frontend, statistics-backend, statistics-frontend, renames MONGOURI → RHMONGOURI on restheart, bumps EREGISTRATIONSVERSION and BUILDTYPE to the values the rest of the chain expects (non-dev: 2.14 / RC; dev: DEV / DEV). Keycloak Quarkus migration is mandatory — when Wildfly env vars are detected on the keycloak service block, the skill replaces them with the Quarkus block (KCDB, KCHOSTNAME) without prompting; this is a hard requirement of the 2.14 baseline, not an optional cleanup. Conditionally adds an opensearch-node1 service block plus repoints GRAYLOGELASTICSEARCHHOSTS from $SERVICEHOST:9200 to opensearch-node1:9200 when the graylog service still references the legacy Elasticsearch endpoint. Strict mode — aborts on anything unexpected. Env-aware anomaly thresholds. LIVE invocations require a retype-country confirmation rail before commit (skipped in chain mode — the orchestrator does it once up front). Two invocation modes: standalone (creates branch, pushes, opens PR) and chain mode (CHAINMODE=1 CHAINBRANCH= , commits to orchestrator-managed branch, no push, no PR). Swarm-stack (docker-stack.yml) shape only — instances still on docker-compose.yml must run /docker-swarm-migration first.
English
AGENT SKILLS ATLASIncludes Bitbucket Jenkins to GitHub Actions, Docker Swarm Migration, Service Manual, and other workflows.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLISupported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Bitbucket Jenkins to GitHub Actions
Migrate a repository from Bitbucket+Jenkins to GitHub+GitHub Actions, including git history, branches, tags, CI/CD pipeline conversion (Jenkinsfile → ci-cd.yml), helm chart updates, branch deletion ruleset, and post-migration validation. Asks clarifying questions and handles external dependencies interactively. Use when migrating UNCTAD-eRegistrations repos from Bitbucket to GitHub.
Docker Swarm Migration
Convert Docker Compose files to Docker Swarm stack format for eRegistrations deployments. Handles env var replacement, secrets management, init-swarm.sh generation, reference stack validation, and dry-run preview. Use when migrating docker-compose.yml to docker-stack.yml, adding deploy sections, configuring overlay networks, or converting environment secrets to Docker Swarm secrets.
Service Manual
Generate a citizen-facing HTML user manual for ONE specific eRegistrations service. Use when the user provides a service ID or BPA URL, asks to "document a service", "create a manual for [service name]", "generate user guide for [service]", "manual for service [name]", or "manual for [service] in [instance]". Do NOT use when the user wants ALL services documented (use /service-manual-all) or wants a technical Excel analysis (use /eregistrations-docs).
Upgrade 2.13 to 2.14
Upgrade a single eRegistrations instance under Conf- /compose/ /docker-stack.yml from 2.13 to 2.14, where is one of dev/test/preview/prelive/live. This is the largest mechanical step in the chain: bumps every unctad/ :$ VER (or pinned semver) image to :RC (the platform tag introduced in 2.14), drops the legacy Keycloak /auth path from internal and public URLs across bpa-frontend, bpa-backend, camunda, mule, ereg-cms-frontend, statistics-backend, statistics-frontend, renames MONGOURI → RHMONGOURI on restheart, bumps EREGISTRATIONSVERSION and BUILDTYPE to the values the rest of the chain expects (non-dev: 2.14 / RC; dev: DEV / DEV). Keycloak Quarkus migration is mandatory — when Wildfly env vars are detected on the keycloak service block, the skill replaces them with the Quarkus block (KCDB, KCHOSTNAME) without prompting; this is a hard requirement of the 2.14 baseline, not an optional cleanup. Conditionally adds an opensearch-node1 service block plus repoints GRAYLOGELASTICSEARCHHOSTS from $SERVICEHOST:9200 to opensearch-node1:9200 when the graylog service still references the legacy Elasticsearch endpoint. Strict mode — aborts on anything unexpected. Env-aware anomaly thresholds. LIVE invocations require a retype-country confirmation rail before commit (skipped in chain mode — the orchestrator does it once up front). Two invocation modes: standalone (creates branch, pushes, opens PR) and chain mode (CHAINMODE=1 CHAINBRANCH= , commits to orchestrator-managed branch, no push, no PR). Swarm-stack (docker-stack.yml) shape only — instances still on docker-compose.yml must run /docker-swarm-migration first.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Bitbucket Jenkins to GitHub Actions skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.