agentleFS
jschullerjschuller/sn-app-template/.agents/skills/deploy-and-verify/SKILL.md

deploy-and-verify

Skill1 starsChanged 23 days agoMITView on GitHub

Build, deploy and verify this ServiceNow app on a development instance — lint, build, now-sdk install, the ATF suite through now-sdk cicd, and REST smoke checks. Use when the user asks to deploy, install, push to an instance, run ATF tests, or check that a change works on ServiceNow.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. ryanramtin/claude-skills★ 1same name
    2. startupsandcode/agent-skills★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

Files
SKILL.md

Deploy and verify

Deploy only to a development or test instance the user named, with a now-sdk auth alias they created. Never to production (production gets the published app through the App Repo: npx now-sdk explain ci-integration). Never print, log or store credentials.

  1. Pre-flight — npm run lint && npm run build. Fix errors before deploying. Confirm the scope in now.config.json carries the target instance's vendor prefix (instances refuse other vendors' prefixes; npm run setup renames it).
  2. Find the alias — npx now-sdk auth --list; ask the user which alias to use if more than one fits.
  3. Install — npm run deploy -- --auth <alias>. Install is asynchronous; the CLI prints a rollback link on success. On "Could not determine app installation status", check the execution tracker link first; do not retry with --reinstall on your own. --reinstall uninstalls the app first, which deletes everything on the instance that is not in source (records in the app's tables, instance-only changes). Explain that to the user, name the instance, and wait for their explicit approval before you retry once with --reinstall. On "Unable to install third party application", see step 1.
  4. ATF — npm run test:instance -- --auth <alias> -o json. If it answers "Scheduled test/suite execution is disabled", the instance needs sn_atf.runner.enabled and then sn_atf.schedule.enabled set to true — ask the user before changing instance properties. Report the pass/fail counts and the result URL.
  5. REST smoke (optional) — in a browser session on the instance, the UI page x_snc_example_app.do must list items; a user without x_snc_example.user must get HTTP 403 from /api/x_snc_example/example_api/items.
  6. Report — what was installed (version from package.json), the ATF result, and anything not verified.

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.