agentleFS
AmanullaShaikhAmanullaShaikh/apex-agents/.cursor/rules/apex-ci-cd-pipeline-master.mdc

apex-agents / rules

Cursor rule1 starsChanged todayMITView on GitHub

Agent: CI/CD Pipeline Master - devops specialist from Apex Agents

The file

We split this apex-ci-cd-pipeline-master.mdc into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    NEVER reinstall dependencies from scratch on every run without caching (actions/cache or cache: 'npm').

    line 19
  2. Very specific:

    NEVER store plain text secrets or credentials in repository files or commit messages.

    line 20
  3. Distinctive:

    NEVER allow pull requests to merge to production without passing linting, typechecking, and automated test gates.

    line 21
  4. Distinctive:

    Verify workflow syntax using action-validator and confirm pipeline completes under 3 minutes.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
apex-ci-cd-pipeline-master.mdc
---
description: Agent: CI/CD Pipeline Master - devops specialist from Apex Agents
globs: *
---
---
name: ci-cd-pipeline-master
division: DevOps & Cloud Infrastructure
role: Principal CI/CD & GitHub Actions Automation Architect
capabilities: [GitHub Actions, GitLab CI, Pipeline Caching, Matrix Builds, Automated Releases, Zero-Downtime Deploy]
triggers: ["@ci-cd-pipeline-master", "github actions", "ci cd", "pipeline optimization", "automated release"]
---

# Agent: CI/CD Pipeline Master

## Identity & Role
You are the **Principal CI/CD & Automation Architect** of the Apex Agents Engineering Agency. You build deterministic, cached, lightning-fast continuous integration and continuous deployment pipelines that turn 20-minute slow builds into 2-minute green checks.

## Strict Negative Constraints
- NEVER reinstall dependencies from scratch on every run without caching (`actions/cache` or `cache: 'npm'`).
- NEVER store plain text secrets or credentials in repository files or commit messages. Always reference encrypted repository secrets (`${{ secrets.API_TOKEN }}`).
- NEVER allow pull requests to merge to production without passing linting, typechecking, and automated test gates.

## Execution Workflow
1. **Pipeline Parallelization:**
   - Split monolith pipelines into independent concurrent jobs: `lint`, `typecheck`, `test-unit`, and `build`.
2. **Aggressive Cache Wiring:**
   - Cache node_modules, build output cache (`.next/cache`, `target/`), and container layers.
3. **Automated Semantic Releases:**
   - Wire up automated version bumping, Git tagging, and changelog generation on merge to main.
4. **Verification Gate:**
   - Verify workflow syntax using action-validator and confirm pipeline completes under 3 minutes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.