Devops Pipeline
luongnv89/skills
Configure pre-commit hooks and lean GitHub Actions for shift-left quality assurance.
Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail.
Install Ways Of Working
$ npx skills add devantler-tech/ksail --skill ways-of-working -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install devantler-tech/ksail ways-of-working --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/devantler-tech/ksail.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/ways-of-working .claude/skills/ways-of-working && 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 "ways-of-working" agent skill from https://github.com/devantler-tech/ksail/tree/main/.agents/skills/ways-of-working into .claude/skills/ways-of-working/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ways-of-working", 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/devantler-tech/ksail/tree/main/.agents/skills/ways-of-workingType 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 devantler-tech/ksail --skill ways-of-working -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install devantler-tech/ksail ways-of-working --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devantler-tech/ksail.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/ways-of-working .agents/skills/ways-of-working && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ways-of-working" agent skill from https://github.com/devantler-tech/ksail/tree/main/.agents/skills/ways-of-working into .agents/skills/ways-of-working/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ways-of-working", 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 devantler-tech/ksail --skill ways-of-working -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install devantler-tech/ksail ways-of-working --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devantler-tech/ksail.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/ways-of-working .cursor/skills/ways-of-working && 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 "ways-of-working" agent skill from https://github.com/devantler-tech/ksail/tree/main/.agents/skills/ways-of-working into .cursor/skills/ways-of-working/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ways-of-working", 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/devantler-tech/ksail.git --path .agents/skills/ways-of-working--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 devantler-tech/ksail --skill ways-of-working -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install devantler-tech/ksail ways-of-working --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devantler-tech/ksail.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/ways-of-working .gemini/skills/ways-of-working && 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 "ways-of-working" agent skill from https://github.com/devantler-tech/ksail/tree/main/.agents/skills/ways-of-working into .gemini/skills/ways-of-working/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ways-of-working", 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 devantler-tech/ksail ways-of-workingInstalls 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 devantler-tech/ksail --skill ways-of-working -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/devantler-tech/ksail.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/ways-of-working .github/skills/ways-of-working && 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 "ways-of-working" agent skill from https://github.com/devantler-tech/ksail/tree/main/.agents/skills/ways-of-working into .github/skills/ways-of-working/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ways-of-working", 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 devantler-tech/ksail --skill ways-of-working -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install devantler-tech/ksail ways-of-working --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/devantler-tech/ksail.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/ways-of-working .opencode/skills/ways-of-working && 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 "ways-of-working" agent skill from https://github.com/devantler-tech/ksail/tree/main/.agents/skills/ways-of-working into .opencode/skills/ways-of-working/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ways-of-working", 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
ways-of-working- GitHub stars
- 165
- Token cost
- ~2k tokens
- SKILL.md length
- 882 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail.
- Works in 5 steps: Create an issue using the… → Plan — create a structured… → Implement — execute the plan following… → …
- Setting up projects
- SKILL.md covers Development Workflow, Testing, Code Quality Gates (CI) and Problem Solving, plus 6 more sections
- Calls go
What it does
Ways Of Working is an agent skill from devantler-tech/ksail. Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Use when filing issues, planning work, setting up projects, configuring CI/CD, writing tests, debugging, or making architectural decisions.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Container orchestration, CI/CD and Test-driven development. It works with Kubernetes and GitHub. The repository describes itself as: All-in-one Kubernetes SDK: create, manage, and operate clusters across distributions (Kind, K3d, Talos, VCluster) with built-in GitOps, secrets, AI assistant, and MCP server… The licence is Apache-2.0.
When your agent uses it
- Setting up projects
- Configuring CI/CD
- Making architectural decisions
Example prompts
- “Use the ways-of-working skill to codify devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow…”
- “/ways-of-working”
Requirements
- Docker
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Create an issue using the devantler-tech/.github issue templates
- Plan — create a structured implementation plan from the issue before writing code.
- Implement — execute the plan following the practices in this skill (TDD, quality gates, GitHub Flow, CI/CD).
- Manual test — validate behavior hands-on before merging. Focus on UX: output must be well-presented and every piece of feedback (errors…
- Code review (optional) — CI's strict linting, scanning, and quality gates are the primary feedback loop, so manual review is not always…
What it can do on your machine
Read from SKILL.md and the folder at commit 5d6163a. 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
Shell commands in SKILL.md call:
go
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.comtestkube.iorefactoring.gurusemantic-release.gitbook.ioconventionalcommits.orggoreleaser.com
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
Ways Of Working loads about 2k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 882 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 devantler-tech/ksail at commit 5d6163a, republished under its Apache-2.0 licence (© devantler-tech). 882 words, ~2,041 tokens.
Download SKILL.mdSave it as
.claude/skills/ways-of-working/SKILL.md (or your agent's skills folder).- name
- ways-of-working
- description
- Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Use when filing issues, planning work, setting up projects, configuring CI/CD, writing tests, debugging, or making architectural decisions.
- license
- Apache-2.0
- metadata.github-path
- ways-of-working/SKILL.md
- metadata.github-ref
- refs/tags/v1.0.0
- metadata.github-repo
- https://github.com/devantler-tech/agent-skills
- metadata.github-tree-sha
- 9a47a2db8c9bdf70402d1790fd3004af517cafe3
- metadata.internal
- true
Ways of Working
Development Workflow
Development is agent-first — every change starts as a structured issue and flows through issue → plan → implement → test → review:
- Create an issue using the devantler-tech/.github issue templates:
- Feature — user story with acceptance criteria.
- Bug — expected vs actual behavior with reproduction steps.
- Chore — user story with acceptance criteria for general tasks.
- Kata — Improvement Kata for continuous improvement (problem → definition of awesome → target condition → actions).
- Plan — create a structured implementation plan from the issue before writing code.
- Implement — execute the plan following the practices in this skill (TDD, quality gates, GitHub Flow, CI/CD).
- Manual test — validate behavior hands-on before merging. Focus on UX: output must be well-presented and every piece of feedback (errors, warnings, prompts) must be actionable.
- Code review (optional) — CI's strict linting, scanning, and quality gates are the primary feedback loop, so manual review is not always required.
Testing
Follow the test-driven-development skill rigorously — write the test first, watch it fail, write minimal code to pass.
Application / Library Repositories
| Type | Tooling | When to run |
|---|---|---|
| Unit tests | SDK test frameworks (e.g. go test, xunit, jest) | CI on every PR |
| Integration tests | SDK test frameworks | CI on every PR |
| E2E / system tests | GitHub Actions workflows that exercise the app/binary/service as an end user would | CI on every PR; move to merge_group if the suite becomes too heavy |
| Benchmark tests | SDK benchmark frameworks (e.g. BenchmarkDotNet, go test -bench) | CI on every PR |
Platform / Kubernetes Repositories
For platform engineering work, ksail provides the build → run → publish loop and Testkube runs the actual test suites inside the cluster:
| Type | App-repo equivalent | Tooling | What it does |
|---|---|---|---|
| Linting / scanning | Unit tests | Standard linters & scanners (e.g. kubeconform, kube-linter, Trivy) | Validate manifests statically — no cluster needed |
| Integration tests | Integration tests | Ephemeral local cluster (ksail cluster create) + Testkube | Spin up a Docker cluster, deploy workloads, and run Testkube test suites against them |
| E2E / system tests | E2E / system tests | Ephemeral or real cluster + Testkube | Deploy to a full environment (local or remote) and run end-to-end Testkube test suites |
Platform lifecycle commands:
| Command | Purpose |
|---|---|
ksail project init | Scaffold a new cluster configuration |
ksail cluster create | Spin up the cluster locally (Docker) or on real infrastructure and verify workloads reconcile |
ksail workload push | Push Kubernetes manifests as OCI artifacts to a container registry |
Code Quality Gates (CI)
Every pull request must pass:
- Strict linting — language-specific linters with zero-tolerance for warnings.
- Strict security scanning — e.g. CodeQL, Trivy, zizmor.
- Strict code quality scanning — e.g. SonarQube, MegaLinter.
- No code coverage regression — coverage must not decrease compared to the base branch.
- No benchmark regression — benchmark results must not regress compared to the base branch.
Problem Solving
- Fix at the root cause — never patch symptoms. Trace every bug or failure to its origin and fix it there.
- Workarounds are always temporary — if a workaround is unavoidable, mark it clearly (e.g.
// WORKAROUND:comment with a linked issue) and schedule its removal. - Upstream first — when a fix belongs in a dependency or upstream project, contribute it there. Only carry a local patch until the upstream change is released.
Libraries
Prefer popular, well-maintained third-party libraries over writing custom implementations. Only roll your own when no suitable library exists or when the dependency would be disproportionately heavy.
Show full SKILL.md (348 more words)Show less
Refactoring & Design
Follow https://refactoring.guru guidelines for refactoring techniques and design patterns.
Branching & Flow
Use GitHub Flow:
- Create a feature branch from
main. - Open a pull request.
- Pass all CI checks.
- Merge via merge queue (
merge_group) when the repository is configured for it; otherwise merge the pull request normally.
CI/CD Pipeline
Each repository has two core workflow files — ci.yaml and cd.yaml — plus a thin release.yaml that calls a reusable workflow (see Releases). Reusable logic is extracted into local GitHub Actions under .github/actions/:
- Composite actions — for simple, self-contained steps.
- TypeScript actions — for anything complex, because they are locally testable and avoid hard-to-read bash embedded in YAML.
Application / Library Repositories
| Event | What runs |
|---|---|
pull_request | All tests (unit, integration, E2E, benchmarks), linting, security & quality scanning, coverage & benchmark regression checks. Move E2E to merge_group only if the suite becomes too heavy. |
merge_group | CD to dev environment. |
push to main | Publish artifacts (packages, container images, etc.). |
Semver tag (vX.X.X) | CD to prod environment. |
Platform / Kubernetes Repositories
| Event | What runs |
|---|---|
pull_request | Linting & scanning (kubeconform, kube-linter, Trivy, etc.) plus integration tests on an ephemeral local cluster (ksail cluster create + Testkube). Move integration tests to merge_group if the suite becomes too heavy. |
merge_group | CD to dev — deploy to staging infrastructure (e.g. Hetzner). |
Semver tag (vX.X.X) | CD to prod — ksail cluster update, ksail workload push, ksail workload reconcile. |
Releases
Releases are automated via the devantler-tech/reusable-workflows/.github/workflows/create-release.yaml reusable workflow. It runs semantic-release on push to main, calculates the next semver from conventional commit history, and creates the tag + GitHub release — which in turn triggers the CD pipeline above.
For application publishing, always use upstream releasers — e.g. GoReleaser for Go or dotnet-releaser for .NET — rather than hand-rolling publish scripts.
Data-Driven Improvement
- Use benchmarking data to guide performance improvements — don't optimise without numbers.
- Use code coverage data to guide where to add tests — target uncovered paths, not a vanity percentage.
Reference Implementations
- devantler-tech/ksail — Go CLI built with TDD, full CI/CD pipeline, benchmarks, and E2E system tests in GitHub Actions.
- devantler-tech/platform — Kubernetes platform using ksail for init → create → push OCI workflow, with progressive CI (Docker → Hetzner staging → Hetzner prod).
© devantler-tech, Apache-2.0. 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/ways-of-working of devantler-tech/ksail.
Open the folder on GitHubat commit 5d6163a
Compare with similar skills
Ways Of Working 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 |
|---|---|---|---|---|---|---|
| Ways Of Working this skilldevantler-tech/ksail | 165 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Devops Pipelineluongnv89/skills | 131 | — | ~4.8k | Automated safety check: Pass | MIT | |
| Project Referencesaiskillstore/marketplace | 433 | — | ~2.3k | Automated safety check: Notes | None | |
| GitHub Runnermagnus919/agent-skills | 115 | — | ~1.7k | Automated safety check: Pass | MIT | |
| KubeSphere DevOps Overviewkubesphere/kubesphere | 17k | — | ~3.1k | Automated safety check: Pass | Custom licence | |
| Release And CIeser/stack | 128 | — | ~665 | Automated safety check: Pass | Custom licence |
Similar skills
Project References
aiskillstore/marketplace
Look up conventions, patterns, and concrete implementations from your own GitHub repositories checked out locally under ~/projects/referenzen/.
GitHub Runner
magnus919/agent-skills
Deploy, manage, and troubleshoot self-hosted GitHub Actions runners.
KubeSphere DevOps Overview
kubesphere/kubesphere
Explains the KubeSphere DevOps extension: Jenkins-based CI/CD, ArgoCD GitOps, how DevOps projects map to namespaces, and project naming rules.
Release And CI
eser/stack
Releases and CI for eserstack: the shared version of all packages, the release command, the tag-driven build.yml run, JSR and npm publishing, changelog and breaking changes, release recovery, GitHub…
GreptimeDB Fuzz CI Failure Investigation
GreptimeTeam/greptimedb
Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.
More from devantler-tech/ksail
Astro
devantler-tech/ksail
Skill for building with the Astro web framework. An agent skill from devantler-tech/ksail.
Bubbletea
devantler-tech/ksail
Build terminal user interfaces with Go and Bubbletea framework.
GitHub Actions Docs
devantler-tech/ksail
A skill your agent uses when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows…
Ksail
devantler-tech/ksail
Use the ksail CLI to spin up and manage Kubernetes clusters (Kind/K3d/Talos/vCluster/KWOK — local via Docker; EKS — cloud via AWS) and GitOps workloads declaratively.
Maintain
devantler-tech/ksail
Repository maintenance for devantler-tech/ksail — triage, bug fixes, CI/workflow health & CI-failure/flaky investigation, docs upkeep, driving every open PR (external contributions included) to a…
Related
Works with
Categories
Questions about Ways Of Working
What does Ways Of Working do?
Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail. Ways Of Working is an agent skill from devantler-tech/ksail. Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail.
When should I use Ways Of Working?
Ways Of Working fits situations like: setting up projects; configuring CI/CD; making architectural decisions.
How do I install Ways Of Working in Claude Code?
Run `npx skills add devantler-tech/ksail --skill ways-of-working -a claude-code`. Or copy the skill folder (.agents/skills/ways-of-working in devantler-tech/ksail) into .claude/skills/ways-of-working in your project. Claude Code loads it when a task matches its description.
How do I install Ways Of Working in Codex?
Run `npx skills add devantler-tech/ksail --skill ways-of-working -a codex`. Or copy the skill folder (.agents/skills/ways-of-working in devantler-tech/ksail) into .agents/skills/ways-of-working in your project. Codex loads it when a task matches its description.
Can I use Ways Of Working 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 devantler-tech/ksail --skill ways-of-working -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ways-of-working, .gemini/skills/ways-of-working, .github/skills/ways-of-working and .opencode/skills/ways-of-working in your project.
What does Ways Of Working need to run?
Going by SKILL.md and its folder, Ways Of Working needs the command-line tools its instructions call (go). Our summary lists: Docker.
Does Ways Of Working access the network?
SKILL.md names 6 domains. As links in the text: github.com, testkube.io, refactoring.guru, semantic-release.gitbook.io, conventionalcommits.org and goreleaser.com. This is read from the text; nothing was executed.
Is Ways Of Working 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 Ways Of Working use?
Ways Of Working is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ways Of Working use?
About 2k tokens (SKILL.md is roughly 8.2k 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 Ways Of Working?
Skills that share tags, products or a category with Ways Of Working: Devops Pipeline (luongnv89/skills, 131 stars), Project References (aiskillstore/marketplace, 433 stars), GitHub Runner (magnus919/agent-skills, 115 stars) and KubeSphere DevOps Overview (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ways Of Working?
devantler-tech (a GitHub organization) maintains it in devantler-tech/ksail, which has 165 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 10, 2026.
Source: devantler-tech/ksail on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.