Devops Deploy
sickn33/agentic-awesome-skills
DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.
Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials.
Install DDNS Build and Release Maintenance
$ npx skills add NewFuture/DDNS --skill build-release-maintenance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NewFuture/DDNS build-release-maintenance --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/build-release-maintenance .claude/skills/build-release-maintenance && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "build-release-maintenance" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/build-release-maintenance into .claude/skills/build-release-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-release-maintenance", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NewFuture/DDNS/tree/master/.agents/skills/build-release-maintenanceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NewFuture/DDNS --skill build-release-maintenance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NewFuture/DDNS build-release-maintenance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/build-release-maintenance .agents/skills/build-release-maintenance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "build-release-maintenance" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/build-release-maintenance into .agents/skills/build-release-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-release-maintenance", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NewFuture/DDNS --skill build-release-maintenance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NewFuture/DDNS build-release-maintenance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/build-release-maintenance .cursor/skills/build-release-maintenance && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "build-release-maintenance" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/build-release-maintenance into .cursor/skills/build-release-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-release-maintenance", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NewFuture/DDNS.git --path .agents/skills/build-release-maintenance--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NewFuture/DDNS --skill build-release-maintenance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NewFuture/DDNS build-release-maintenance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/build-release-maintenance .gemini/skills/build-release-maintenance && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "build-release-maintenance" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/build-release-maintenance into .gemini/skills/build-release-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-release-maintenance", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NewFuture/DDNS build-release-maintenanceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NewFuture/DDNS --skill build-release-maintenance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/build-release-maintenance .github/skills/build-release-maintenance && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "build-release-maintenance" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/build-release-maintenance into .github/skills/build-release-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-release-maintenance", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NewFuture/DDNS --skill build-release-maintenance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NewFuture/DDNS build-release-maintenance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NewFuture/DDNS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/build-release-maintenance .opencode/skills/build-release-maintenance && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "build-release-maintenance" agent skill from https://github.com/NewFuture/DDNS/tree/master/.agents/skills/build-release-maintenance into .opencode/skills/build-release-maintenance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-release-maintenance", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
build-release-maintenance- GitHub stars
- 4.7k
- Token cost
- ~444 tokens
- SKILL.md length
- 203 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials.
- Works in 8 steps: Read the root AGENTS.md and the current… → Treat current workflow inputs,… → Identify the affected artifact and… → …
- Fixing a failing build in the DDNS GitHub Actions workflows
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Changing Docker or Nuitka packaging without dropping platforms
What it does
The agent starts from the root AGENTS.md and the files involved: the workflows folder, docker folder, .github/patch.py, run.py, pyproject.toml and the relevant test scripts. It treats current workflow inputs, Dockerfiles, lockfiles and pinned settings as the source of truth rather than remembered versions, and identifies the affected artifact and platform set before editing. Python source, wheels and sdist, native binaries, Linux libc variants, containers, installers and scheduled-task validation are preserved unless the task changes support.
Changes are kept narrow: pull-request cache access stays restore-only, shared caches are written only from trusted branches, and compression, LTO, tests, caching or a platform are not disabled globally to fix one architecture failure without evidence. Existing build and offline end-to-end scripts are reused, and required checks stay independent of deployed sites. Release preparation verifies version changes, artifact names, checksums, release notes and rerun idempotency, then the agent runs the affected checks and reports matrix entries it did not exercise. It never publishes to PyPI, registries or GitHub Releases, and never touches release credentials or protected environments.
When your agent uses it
- Fixing a failing build in the DDNS GitHub Actions workflows
- Changing Docker or Nuitka packaging without dropping platforms
- Preparing a release and checking versions, artifact names and checksums
- Reviewing cache or matrix changes in CI
Example prompts
- “The ARM container build is failing in CI. Find the cause and change as little as possible.”
- “Prepare the next release and check the artifact names and checksums.”
- “Add a new Linux libc variant to the Nuitka build matrix without touching the existing ones.”
Requirements
- A checkout of the DDNS repository
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Read the root AGENTS.md and the current files involved in the task
- Treat current workflow inputs, Dockerfiles, lockfiles, and pinned settings as
- Identify the affected artifact and platform set before editing. Preserve
- Keep pull-request cache access restore-only and write shared caches only from
- Make the narrowest coherent change. Do not disable compression, LTO, tests,
- Reuse existing build and offline E2E scripts. Keep required pull-request
- For release preparation, verify version transformations, expected artifact
- Run the affected package, binary, container, installer, and platform checks,
What it can do on your machine
Read from SKILL.md and the folder at commit 1c17f4e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
DDNS Build and Release Maintenance loads about 444 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 203 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NewFuture/DDNS at commit 1c17f4e, republished under its MIT licence (© NewFuture). 203 words, ~444 tokens.
Download SKILL.mdSave it as
.claude/skills/build-release-maintenance/SKILL.md (or your agent's skills folder).- name
- build-release-maintenance
- description
- Maintain DDNS GitHub Actions, Docker and Nuitka builds, packaging, installer validation, and release preparation while preserving matrices, caches, and protected publishing.
Build and Release Maintenance
- Read the root
AGENTS.mdand the current files involved in the task:.github/workflows/,docker/,.github/patch.py,run.py,pyproject.toml, and relevant test scripts. - Treat current workflow inputs, Dockerfiles, lockfiles, and pinned settings as the source of truth. Do not rely on remembered versions, images, runners, or matrices.
- Identify the affected artifact and platform set before editing. Preserve Python source, wheel/sdist, native binaries, Linux libc variants, containers, installers, and scheduled-task validation unless the task explicitly changes support.
- Keep pull-request cache access restore-only and write shared caches only from trusted branches.
- Make the narrowest coherent change. Do not disable compression, LTO, tests, caching, or a platform globally to solve one architecture failure without evidence that the policy should change.
- Reuse existing build and offline E2E scripts. Keep required pull-request checks independent of deployed websites and external mutable services.
- For release preparation, verify version transformations, expected artifact names, checksums, release notes, and rerun idempotency.
- Run the affected package, binary, container, installer, and platform checks, then report any matrix entries not exercised.
Do not publish to PyPI, container registries, or GitHub Releases. Do not access release credentials, modify repository settings, bypass protected environments, or weaken required checks.
© NewFuture, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/build-release-maintenance of NewFuture/DDNS.
Open the folder on GitHubat commit 1c17f4e
Compare with similar skills
DDNS Build and Release Maintenance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| DDNS Build and Release Maintenance this skillNewFuture/DDNS | 4.7k | — | ~444 | Automated safety check: Pass | MIT | |
| Devops Deploysickn33/agentic-awesome-skills | 47k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Code PatternsAedelon/claude-code-blueprint | 120 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Deployment and CI/CD Patternsaffaan-m/ECC | 275k | 6 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Devops InfrastructureCloudAI-X/claude-workflow-v2 | 1.4k | — | ~2.7k | Automated safety check: Notes | MIT |
Similar skills
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Code Patterns
Aedelon/claude-code-blueprint
Reference patterns for REST APIs, pytest/vitest testing, Docker multi-stage builds, GitHub Actions CI/CD, PostgreSQL, TypeScript generics, Python async, and React Server Components.
Deployment and CI/CD Patterns
affaan-m/ECC
Covers rolling, blue-green and canary deployments, multi-stage Dockerfiles, a GitHub Actions pipeline, health checks and production readiness for web apps.
Devops Infrastructure
CloudAI-X/claude-workflow-v2
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup.
CI/CD Pipeline Principles
irahardianto/awesome-agv
Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.
More from NewFuture/DDNS
DDNS Provider Development
NewFuture/DDNS
Adds or changes a DNS provider in the DDNS project while keeping its code, schemas, tests and Chinese and English docs consistent.
DDNS VitePress Docs Maintenance
NewFuture/DDNS
Maintain DDNS VitePress documentation with bilingual parity, correct navigation and links, safe executable-doc changes, and build verification.
CI Failure Triage
NewFuture/DDNS
Diagnose and fix required CI failures for the current DDNS branch without weakening tests, platform coverage, caches, or repository policy.
Related
Works with
Categories
Questions about DDNS Build and Release Maintenance
What does DDNS Build and Release Maintenance do?
Maintains the DDNS project's GitHub Actions, Docker and Nuitka builds, packaging and release preparation without touching publishing credentials. toml and the relevant test scripts. It treats current workflow inputs, Dockerfiles, lockfiles and pinned settings as the source of truth rather than remembered versions, and identifies the affected artifact and platform set before editing.
When should I use DDNS Build and Release Maintenance?
DDNS Build and Release Maintenance fits situations like: fixing a failing build in the DDNS GitHub Actions workflows; changing Docker or Nuitka packaging without dropping platforms; preparing a release and checking versions, artifact names and checksums; reviewing cache or matrix changes in CI.
How do I install DDNS Build and Release Maintenance in Claude Code?
Run `npx skills add NewFuture/DDNS --skill build-release-maintenance -a claude-code`. Or copy the skill folder (.agents/skills/build-release-maintenance in NewFuture/DDNS) into .claude/skills/build-release-maintenance in your project. Claude Code loads it when a task matches its description.
How do I install DDNS Build and Release Maintenance in Codex?
Run `npx skills add NewFuture/DDNS --skill build-release-maintenance -a codex`. Or copy the skill folder (.agents/skills/build-release-maintenance in NewFuture/DDNS) into .agents/skills/build-release-maintenance in your project. Codex loads it when a task matches its description.
Can I use DDNS Build and Release Maintenance in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NewFuture/DDNS --skill build-release-maintenance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-release-maintenance, .gemini/skills/build-release-maintenance, .github/skills/build-release-maintenance and .opencode/skills/build-release-maintenance in your project.
What does DDNS Build and Release Maintenance need to run?
SKILL.md names no scripts, command-line tools or credentials: DDNS Build and Release Maintenance is instructions for the agent only. Our summary lists: A checkout of the DDNS repository.
Does DDNS Build and Release Maintenance access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is DDNS Build and Release Maintenance safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does DDNS Build and Release Maintenance use?
DDNS Build and Release Maintenance is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does DDNS Build and Release Maintenance use?
About 444 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to DDNS Build and Release Maintenance?
Skills that share tags, products or a category with DDNS Build and Release Maintenance: Devops Deploy (sickn33/agentic-awesome-skills, 47k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Code Patterns (Aedelon/claude-code-blueprint, 120 stars) and Deployment and CI/CD Patterns (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains DDNS Build and Release Maintenance?
NewFuture (a GitHub user) maintains it in NewFuture/DDNS, which has 4,696 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: NewFuture/DDNS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.