Skip to content
cccskills
FreePublished on GitHub

deploy-landed

Prove a deploy landed — the served revision is the commit you meant, its env is present, and the product does its job — instead of trusting the deploy command's exit code. Also catches server drift before a pull or deploy. Use after any deploy, rollout, restart or server-side fix ("задеплой", "выкати", "проверь на проде", "почему не обновилось"). Loaded by devops, l3-support, infra-provisioner.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto
See how to install

Files included (1)

  • SKILL.md4.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

deploy-landed — a deploy is done when the running thing is the thing you meant

A deploy command's exit code says the command finished. It does not say the new code is serving, that its configuration arrived, or that the product works. Every trap below produced a green exit and a broken or stale product on a real project:

TrapWhat happened
git pull failed, the build went onThe build succeeded from the old code and reported success
nohup … &Exit 0 twice for a process that died at once
docker exec into a containerIt does not inherit the entrypoint's env: two "config is missing" readings were false
sed -i / docker cp on a bind-mounted fileReplaced the inode; the container kept reading the old file
A fix applied only on the serverLost on the next deploy — it was never in git
wrangler / Pagesfunctions/ not deployed, _headers ignored, five deploys to notice
Prod behind SSOAnswers 401/302 to every path, including ones that do not exist — proves nothing about a route
/health greenFor six hours while the engine made no trades

Before: is the server what git says it is?

Before pulling or building on a host someone can reach by hand:

git -C /srv/app status --porcelain        # anything here is a patch that is not in git
git -C /srv/app log -1 --format=%H        # what the host thinks it runs

Anything uncommitted on the host is either committed first or reported as drift — never overwritten silently, and never left as the only copy of a fix.

After: four checks, each with its evidence

  1. Revision. What is serving equals the commit you meant.
    • Cloud Run / k8s: the live revision's image tag or digest, then git merge-base --is-ancestor <commit> <image-tag-sha>.
    • Pages / Workers / Vercel: the deployment id and its commit.
    • A plain host: the running process's start time is after the deploy, and the file it serves has the new content (grep for a string the change introduced).
    • A /version endpoint, when the app has one, beats all of the above.
  2. Configuration. The variables and secrets the new code reads are present in the running process — count them against the list the code expects. In a container, read them from PID 1 (cat /proc/1/environ | tr '\0' '\n'), not from docker exec env. After --set-secrets/--set-env-vars, check that the ones you did not name are still there: those flags replace the whole set.
  3. Function. One request that does the product's job and returns something you can compare to a known value — an order created, a row written, a trade placed on paper. A health endpoint proves the process is up, nothing more.
  4. Startup errors. Logs for the new revision since it started, at WARNING and above. Zero lines is a finding only if you saw the logs flowing at all.

Report

End the deploy report with this block. A check you could not run is NOT CHECKED with the reason — never omitted, never PASS.

DEPLOY-LANDED <service> @ <commit>
  revision : PASS — serving <revision/deployment id> built from <sha>
  config   : PASS — 14/14 expected vars present in PID 1
  function : PASS — POST /orders → 201, row id 8812 visible in DB
  startup  : PASS — 0 WARNING+ lines since 12:04:10

A FAIL in any line means the deploy is not done, whatever the command printed.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

aesthetic-instrument

Free

great_cto's own committed aesthetic — the instrument panel. Dark five-step surface ladder, exactly one accent, two faces divided by MEANING (Geist speaks, Geist Mono is machine-truth), tabular numerals, and a dash that is not a nought. Twelve checkable rules measured from packages/board and greatcto.systems, not designed for this file. Use when building or extending any great_cto surface — the board, the site, a report, a share page.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 23, 2026

anti-patterns

Free

Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 23, 2026

anydesign

Free

Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does this site use', 'how is this built'. Also for single elements: 'copy this navbar', 'recreate this illustration', 'give me a prompt to regenerate this graphic' — element mode outputs a focused element.md, with token-grounded image-model prompts when the element is visual art. If the user brings any visual source and wants to understand it at a design level — this skill should activate.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 23, 2026

archetype-review-base

Free

Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 23, 2026

brainstorming

Free

Structured idea generation + multi-LLM debate for the product-owner stage. Diverge (generate genuinely different bets), debate (a 4-persona panel on 4 models argues over 2 rounds), converge (synthesize a recommendation). Used by product-owner before architect; available to architect for design-space exploration.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 23, 2026

codex-host

Free

Run the great_cto controlled Codex lifecycle with controller-owned writes, verifier evidence, human gates and optional artifact release.

The English summary is being prepared. Showing the original description.

avelikiy/great_cto105Updated Oct 23, 2026

See all skills by avelikiy

Report a problem with this skill