Collection devops

outils d’automatisation pour opérations DevOps | AI Agent Skills

Collection de AI Agent Skills installables pour les workflows développeur devops operations automation dans Claude Code, Cursor et Windsurf.

Cette collection vise les équipes qui exploitent des logiciels en production. Elle couvre l’automatisation DevOps sur les releases, la gestion d’infrastructure, le traitement des alertes et les routines de fiabilité afin de réduire le travail manuel et d’accélérer la réponse aux changements. MCP peut être utilisé comme option d’intégration, mais l’axe principal reste l’excellence opérationnelle.

Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from DevOps discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path

Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.

P1 solution

Process Automation Solution

A solution page for teams turning SOPs, handoffs, and operations into repeatable AI-assisted execution paths.

Operational intent deserves a stronger bridge than generic tooling lists can provide.

P1 solution

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against DevOps workflow fit, installation clarity, operator handoff, and production operations usefulness. This page is now positioned as an install-first DevOps entry point instead of a broad automation roundup.

We prioritize this page because DevOps-intent users usually need a shortlist they can install, validate, and carry into real release and incident loops quickly.

Trust Signals

- Entries are chosen for practical DevOps workflow value such as release operations, incident response, platform maintenance, and operator clarity.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable operations execution, not for vague automation keyword coverage or generic repository popularity.

Grouping Logic

- Lead with tools that can enter a DevOps-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering releases, incidents, platform care, and automation support.
- Use installation as the bridge from DevOps discovery into validated daily execution.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or DevOps workflow relevance changes upstream; otherwise review monthly.
Maintained By: Killer-Skills editorial review within the recovery-focused authority queue.
Verification: Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Execution Examples

How These Skills Work Together In Practice

Install one DevOps workflow tool first

Use this page when you want one DevOps companion that can enter real production work without turning evaluation into another endless tooling audit.

1. Open the installation docs before opening more DevOps-related repositories.
2. Choose one tool that best supports release operations, incidents, automation, or platform maintenance.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider DevOps workflow.

Reduce platform operations drag

Treat the collection as an editorial filter when you need DevOps-adjacent tools that improve operational confidence without overcomplicating the stack.

1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more environments, services, or teammates.
4. Document the chosen DevOps workflow baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check workflow choices before you standardize a team stack.

declutter

wildcard

caro: fast Rust CLI that turns natural‑language tasks into a safe POSIX command. Built for macOS (MLX/Metal) with a built‑in model; supports vLLM/Ollama/LM Studio. JSON‑only output, safety checks, confirmation, multi‑step goals, devcontainer included.

★ 27

⑂ 0

Intelligence artificielle

setup-dev

[ Officiel ]

getsentry

Set up and manage the Sentry development environment using devenv. Handles fresh setup, updating existing environments, starting dev services, and troubleshooting. Use when asked to set up sentry, setup dev environment, get sentry running, start dev server, devenv setup, devservices not working, sentry wont start, or any development environment issue.

★ 43.2k

⑂ 0

DevOps & Cloud

sentry-javascript-bugs

[ Officiel ]

getsentry

Sentry JavaScript frontend bug pattern review based on real production errors. Use when reviewing React/TypeScript frontend code for common bug patterns. Trigger keywords: javascript bug review, frontend errors, react error patterns, sentry frontend bugs.

★ 43.2k

⑂ 0

DevOps & Cloud

fix_bug

pgplex

Fix a bug from a GitHub issue using TDD. Analyzes the issue, creates a reproducing test case, implements the fix, verifies it, runs refactor-pass, and creates a PR.

★ 808

⑂ 0

Développeur

Related Authority Collections

If This Page Is Close, Keep Narrowing With Adjacent Authority Pages

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

P2 collection

Rust Workflow Tools to Install First

A systems-focused Rust collection for teams evaluating reliability, release, and guardrail workflows.

Rust traffic is more valuable when it lands on a systems-aware shortlist instead of a generic language wrapper.

P1 collection

Agent Framework Tools to Install First

A framework and SDK collection for teams building agent foundations, not just browsing vendor names.

Framework intent strengthens the site's product judgment and reduces the mirror-site posture.

P1 collection

Python Workflow Tools to Install First

A Python engineering collection built for teams choosing installable workflow helpers instead of browsing raw packages.

Python demand converts better when the site looks like an install guide with judgment, not a bulk package mirror.

P1 collection

Next.js Workflow Tools to Install First

A full-stack workflow collection for Next.js teams that need a faster path from evaluation into install and rollout.

Framework-specific collections create stronger topical authority than broad developer-tool roundups.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

Pour quels flux de travail ces collections sont-elles conçues ?

Ces collections sont conçues autour de l'automatisation de flux, processus, documents, données et piles de compétences réutilisables.

Quelle est la différence entre une collection et le répertoire principal ?

Le répertoire est meilleur pour la recherche directe, tandis que les collections regroupent des compétences complémentaires autour d'un flux complet.

Puis-je installer ces collections pour Claude Code ou Cursor ?

Oui. Les compétences de ces collections fonctionnent généralement dans Claude Code, Cursor, Windsurf et d'autres environnements via un flux d'installation unifié.

Additional Recovery Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.

P0 collection

Agent Workflow Building Tools

A workflow-first collection that explains why related skills belong together and what job they solve.

Workflow collections add first-party judgment that generic skill detail pages struggle to communicate.