post-deploy
Skill0 starsChanged 5 months agoMITView on GitHub
Use when verifying deployment after code changes to globally linked packages (npm link), running services, daemons, or scheduled tasks. Triggers when code changes affect a globally installed CLI or a running service. Do not use for general development, CI setup, or initial deployments.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- arturseo-geo/cowork-wordpress-publishertheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- arturseo-geo/cowork-wordpress-publisher★ 2same 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.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If the changed repository matches a globally linked package, the agent MUST proceed to rebuild.
- Very specific: line 28
Run the repository's build command (e.g., npm run build, tsc).
- Very specific: line 30
Verify the rebuilt output by running the CLI's --version or a smoke command.
- Distinctive: line 39
Verify with deterministic evidence:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Post-change deployment procedures
Detection
Globally linked packages
- The agent MUST run
npm ls -g --depth=0and look for entries with->pointing to a local path. - If the changed repository matches a globally linked package, the agent MUST proceed to rebuild.
Running services and scheduled tasks
- The agent MUST check for running processes associated with the repository (service names, PM2/systemd/Windows service entries).
- The agent MUST check for scheduled tasks (cron, Windows Task Scheduler) referencing the repository.
Rebuild and verify
npm-linked packages
- Run the repository's build command (e.g.,
npm run build,tsc). - Verify the rebuilt output by running the CLI's
--versionor a smoke command. - Report the verified version.
Services and daemons
- Rebuild the service component.
- Restart using the service manager (PM2 restart, systemctl restart, etc.).
- Verify with deterministic evidence:
- New PID (compare before and after).
- Port check (verify listening).
- Service status query.
- Log entry showing updated behavior or version.
- Report the verification evidence.
Completion gate
- The agent MUST NOT claim completion until the running instance reflects the changes. The agent MUST include verification evidence in the final response.
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.

