lando-check
Skill4 starsChanged 14 days agoMITView on GitHub
Check that a project's local Lando environment is up and serving, start it if not, find the real local URL, and diagnose the usual failures (Docker not running, port already allocated, stale containers, shop redirecting to the production domain). Use when the user says "levanta lando", "está arriba el local?", "verifica en local", "comprueba el sitio local", "no carga el lndo.site", "lando no arranca", "puerto ocupado", or before verifying a change in the browser.
In this repository37 other files it gives its agents.
- blast-radiusSkill
- elementflow-kbSkill
- gitlab-changelog-releaseSkill
- gitlab-ci-quality-gatesSkill
- gitlab-project-bootstrapSkill
- gitlab-security-setupSkill
- gitlab-wiki-bootstrapSkill
- lando-img-placeholderSkill
- lando-mail-smtpSkill
- lando-setupSkill
- mallard-releaseSkill
- mr-flowSkill
- no-commentsSkill
- paginated-report-pdfSkill
- panda-kbSkill
- ploi-prestashop-deploySkill
- prestashop-kbSkill
- ps-consoleSkill
- ps-css-buildSkill
- ps-demo-userSkill
- ps-email-previewSkill
- ps-image-regenSkill
- ps-invoice-previewSkill
- ps-new-projectSkill
- ps-one-page-checkoutSkill
- ps-project-docSkill
- ps-security-auditSkill
- ps-storefront-polishSkill
- ps-theme-cacheSkill
- ps-translateSkill
- ps-view-transitionsSkill
- ps-watchSkill
- reflectSkill
- show-me-your-workSkill
- skill-authorSkill
- task-contextSkill
- verify-ps-projectSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
If it is down, open the app the user uses (open -a OrbStack or open -a Docker), wait until docker info succeeds, then continue.
- Very specific: line 41
Not running: lando start 2>&1 | tail -25, then back to step 3.
- Very specific: line 45
Use the URL from lando info (usually https://<name>.lndo.site.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
lando-check
Gets from "is the local site working?" to a verified answer in one pass. It does not set a project up from scratch (use lando-setup for that) and it does not change code.
1. Docker engine
lando needs a running Docker engine (OrbStack or Docker Desktop).
docker info >/dev/null 2>&1 && echo "docker ok" || echo "docker down"If it is down, open the app the user uses (open -a OrbStack or open -a Docker), wait until docker info succeeds, then continue. Do not run lando commands before that.
2. Is this project running?
From the project root (the directory with .lando.yml):
lando info 2>&1 | grep -E 'urls|https?://|service:' | head -20
lando list 2>&1 | grep -i "$(basename "$PWD")" | head- No
.lando.ymlin the directory: stop and say so. Offerlando-setupif the project was never set up locally. - Containers
runningand URLs listed: go to step 3. - Not running:
lando start 2>&1 | tail -25, then back to step 3.
3. Health check
Use the URL from lando info (usually https://<name>.lndo.site; multistore projects have several domains, check each one the user cares about):
curl -sk -o /dev/null -w "%{http_code} %{redirect_url}\n" "https://<name>.lndo.site/"| Result | Meaning | Action | |
200 | Serving | Report OK. | |
301/302 to the production domain | ps_shop_url / .htaccess still point to prod (usual after a DB import) | Fix with the /ps-url command or the DB refresh step of lando-setup. Do not edit prod config. | |
301/302 to http:// or another lndo.site | Wrong scheme or domain mismatch | Check ps_shop_url and the domain in .lando.yml proxy. | |
500 / 502 | PHP or nginx error | `lando logs -s appserver 2>&1 | tail -30` and report the real error. |
| connection refused / timeout | Proxy or containers down | Step 4. |
4. Common failures
port is already allocated/address already in use(usually the MySQLportforwardin.lando.yml, or 80/443 held by another Lando app or a local server):
Tell the user which process/app holds the port. Do not kill processes or stop other projects without asking. If the clash is another project'slsof -nP -iTCP:<port> -sTCP:LISTEN lando list 2>&1 | grep -E 'name|running|port' grep -rn portforward ~/Developer/*/*/.lando.yml 2>/dev/null | headportforward, pick the next free port in this project's.lando.ymland ask before editing.- Stale or half-started app (
lando starthangs or errors on the first try):lando restart; if it persists,lando rebuild -y(asks before it, because it recreates containers; the DB volume is kept). - Browser says certificate error: Lando's CA is not trusted on this machine; the
curl -kcheck still works. Report it, do not change system trust settings.
5. Report
One short block: project, Docker state, containers, URL(s) and HTTP status, and anything the user must fix. If you started Lando, say so.
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
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.