Super engineering devops

Skill arpitexplores/super-engineering-devops

Engineering and DevOps delivery: architecture, build, test, deploy, and operate reliable systems.From its SKILL.md

Install

npx -y skills add arpitexplores/super-engineering-devops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 346 tokens by cl100k_base, as published. Nobody here has run it

Super Engineering/DevOps

Overview

Build and run software with strong architecture, quality, and delivery practices.

User Intent Examples

"Need help with DevOps & Deployment for my product/site."
"Create a plan for Observability."
"Audit or improve Full-Stack Engineering."

Workflow

Clarify requirements, constraints, and success metrics.
Select architecture and core tech stack.
Design data models, APIs, and integration boundaries.
Implement with tests and quality checks.
Set up CI/CD and deployment strategy.
Add observability and runbooks.

Minimal Intake Questions

Primary goal or outcome
Scope (pages, systems, teams, or timeframe)
Constraints (tools, budget, timeline)

Output Format

Architecture and design summary
Implementation plan
Test and QA plan
CI/CD and deployment plan
Observability checklist

Routing Map (Modules)

DevOps & Deployment -> references/modules/devops-deploy.md
Observability -> references/modules/observability-engineer.md
Full-Stack Engineering -> references/modules/senior-fullstack.md

Bundled References

references/modules/
scripts/
assets/
agents/

Compatibility Notes

If any module references slash commands or tool-specific paths, translate them into plain-language steps.
Keep outputs platform-agnostic unless the user specifies a specific tool, stack, or agent.

Guardrails

Do not claim performance gains without measurements.
Keep testing requirements explicit.
Prefer incremental delivery and rollback safety.

What ships with it: 13 files

2413.8 KB alongside SKILL.md

Gives 0 of the 12 instructions most ship operate skills give in 346 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

Clarify requirements, constraints, and success metrics
Select architecture and core tech stack
Design data models, APIs, and integration boundaries
Implement with tests and quality checks
Add observability and runbooks
Translate tool-specific paths into plain-language steps

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.