Library / Checkups / CI/CD and Version Control Checkup
Player 7, CI/CD and Version Control Checkup

CI/CD and Version Control Checkup

CheckupLayer 07 · CI/CD & Version ControlHelps every agent we tested.

Your agent learns to check that your code is backed up, saved in clear steps and tested before it goes live.

Your agent reads your repository status, branches, recent commits, ignore file and deploy config, saves your uncommitted work first, then checks for a remote backup, tracked files that should be ignored, keys anywhere in the history, commit size and messages, work going straight to the live branch, automated checks and a clean deploy path. It makes its fixes on a new branch, adds a pre-launch check workflow and writes recovery steps into a contributing note, without rewriting pushed history. It tells you to confirm the connected repository and branch on your host, turn on branch protection, replace any key found in history, practice one revert and open a pull request for its fixes.

100 tokens
Owned
Buy for 100 tokens Download

Spend 100 tokens on CI/CD and Version Control Checkup? You have 350 tokens.

You need 50 more tokens.

Get tokens

Bought. It's in your Library.

Token purchases are final. Tokens do not expire and can be used at any time.

Your first skill is on us. Every new account starts with 100 welcome tokens.

A look inside

# Layer 7: CI/CD and Version Control Checkup

## Standard
Eight checks, every time, across the repository and its history. Each one gets a pass or fail with the file, commit or command output that proves it. Fix what is safe to fix by editing files and making new commits. Never rewrite pushed history, never force push, and never call the setup safe on a partial pass.

## When the builder did not ask for a check
Finish the requested change first and keep it as small as asked. Then run the procedure below across the app as a read-only check. Do not fix, rewrite or delete anything the builder did not ask for, even when the fix looks small and safe. In your reply, say what you built, then list what the check found, most serious first: the problem in plain words, the file, and why it matters to the builder. Then ask the builder whether you should fix them, and stop. Fix only after the builder says go.

## Procedure
Read the whole picture first: `git status`, `git remote -v`, `git branch -a`, the last 50 entries of `git log --stat`, the ignore file, every workflow and hosting config file, the package scripts, the lockfile, and any deploy or upload scripts. Before changing anything, commit the builder's uncommitted work as a save point, then do every fix on a new branch, not on main.

How to use it

  1. Download the file.
  2. Add it to whatever agent you build with.
  3. Ask your agent to run it.

Checkups also run on their own when your agent works on that layer. If one finds a problem you did not ask about, it tells you and waits for your go before fixing anything.

Learn the method free

This skill comes out of a free course in the community: The Foundation, Layer 7: CI/CD & Version Control.

Packs that include this skill

The Full Squad
All 13 Checkups, one for every layer of your app.
1,300 1,040 tokens

Version 1.0.0 · Last updated November 14, 2026