agentleFS
Sign inStart free
DenchHQDenchHQ/ironclaw/skills/gstack/land-and-deploy/SKILL.md

land-and-deploy

Skill1.7k starsChanged 7 months agoMITView on GitHub

Merge the PR, wait for CI and deploy, verify production health. Takes over after ship. One command from "approved" to "verified in production."

  • Commits and pushes

33 other projects use a version of this.

Trending

Quiet since February.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the DenchHQ/ironclaw repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about DenchHQ/ironclaw

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use landing-report, pair-agent and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 7 projects that use this

  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 9 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 6 projects that use this

  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 7 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 6 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 4 projects that use this

  • +3 more from ShreyRavi

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All CI checks must pass

    line 23
  2. Distinctive:

    Use squash merge by default (clean history).

    line 34
  3. Distinctive:

    Check CI/CD status after merge

    line 42
  4. Distinctive:

    Wait for deploy to complete (poll deployment status)

    line 43
  5. Distinctive:

    If deploy fails, alert the user immediately

    line 44
  6. Distinctive:

    Verify the shipped feature works

    line 53
  7. Distinctive:

    Check for console errors

    line 54
  8. Distinctive:

    Check for network errors

    line 55
  9. Distinctive:

    If something breaks, offer to revert:

    line 72

“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “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
SKILL.md

Land and Deploy — From Approved to Verified

Takes over where ship left off. Merge, deploy, verify.

Related skills: ship | canary | qa

Step 1: Pre-Merge Checks

gh pr checks
gh pr view --json reviewDecision -q .reviewDecision
  • All CI checks must pass
  • PR must be approved (or the user explicitly overrides)

Step 2: Merge

gh pr merge --squash --delete-branch

Use squash merge by default (clean history). If the user prefers merge commits, honor that.

Step 3: Wait for Deploy

Monitor the deployment:

  1. Check CI/CD status after merge
  2. Wait for deploy to complete (poll deployment status)
  3. If deploy fails, alert the user immediately

Step 4: Production Verification

After deploy completes:

  1. Navigate to the production URL
  2. Verify the shipped feature works
  3. Check for console errors
  4. Check for network errors
  5. Screenshot key pages

Step 5: Post-Deploy

DEPLOY REPORT
═══════════════════════════════════════
PR:               #123 (merged)
Deploy status:    SUCCESS
Production URL:   https://app.example.com
Verification:     PASS
═══════════════════════════════════════

If something breaks, offer to revert:

gh pr create --title "Revert: ..." --body "Reverting PR #123 due to ..."

For extended monitoring, use canary.

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.

Check your setup, free