Cursor workflows for DevOps
Cursor was used by a DevOps engineer with rules files, MCP plugins, and auto-run commands to refactor configs, debug builds, and migrate infrastructure code.
The author migrated 10+ Lambda functions from Node.js 14 to 20 in one pass and fixed a broken docker-compose file by auto-retrying until clean.
Overview
How it was set up
Cursor with a .cursorrules file, global rules, Kubernetes and GitHub MCP plugins, a .cursorignore file, notepads for CI/CD templates, and agent auto-run commands enabled.
Worth knowing
Cursor once hallucinated secrets from a .env file until it was ignored. AI changes can go rogue, so the author commits often and saves checkpoints.
A prompt to start from
Fix this Dockerfile for a [language] app. Base image: [image]. Run as non-root user. Add a multistage build for production. Keep size under [size]. Validate with 'docker build --no-cache'.
Written by Agentic Feats from the source. Not the author's exact prompt.
Sources 1
History
- Source published
- 2025-08-23
- Added to Agentic Feats
- 2026-10-13
- Pick
- No
- Markdown copy
- /c/cursor-workflows-for-devops.md
More in ops and IT
20 featsResultProvisioning worked after two fixes. The MCP hid the real errors, so apply ran through Cursor's Run tool, which suggested the fix.
ResultThe author runs 14 containers including Vaultwarden, Immich, Plex, and Readeck, with daily USB and weekly S3 Glacier backups costing about twenty cents per month.
ResultThe initial sort took a few minutes and left no loose files in the main directory, in about 20 minutes of active work.