post-deploy-check
Skill0 starsChanged 32 days agoMITView on GitHub
Owner-invoked check of the installed Preview after an update. Use only when the owner asks to check the installed app, its version or its logs against the "Pending owner checks" list.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mdigital94/vibe-shield-plugintheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mdigital94/vibe-shield-plugin★ 0same 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 repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- convergence-reviewSkill
- ecoSkill
- plan-executionSkill
- planning-and-variantsSkill
- provider-evidenceSkill
- receiving-code-reviewSkill
- security-lifecycleSkill
- systematic-debuggingSkill
- verification-before-completionSkill
- convergence-reviewSkill
- ecoSkill
- plan-executionSkill
- planning-and-variantsSkill
- post-deploy-checkSkill
- provider-evidenceSkill
- receiving-code-reviewSkill
- security-lifecycleSkill
- systematic-debuggingSkill
- verification-before-completionSkill
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 13
Read only. Never sign in, never change the app's settings or data, never install or update.
- Very specific: line 14
Never read credentials, DPAPI stores, provider stores, source-CLI credential stores, or response-* and trace-* log files (they hold …
- Very specific: line 26
Logs: Read only application-*.jsonl and critical-*.jsonl under %LOCALAPPDATA%\Packages\<PackageFamilyName>\LocalState\logs, from the update …
- Distinctive: line 38
Commit the record changes under the Git flow.
≈ “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
post-deploy-check
Decisions R-217 and R-190: the owner's manual and live checks happen in the installed app after deployment. This skill helps the owner close them. It runs only when the owner asks for it.
Boundaries
- Read only. Never sign in, never change the app's settings or data, never install or update.
- Never read credentials, DPAPI stores, provider stores, source-CLI credential stores, or
response-*andtrace-*log files (they hold sanitized provider bodies and verbose detail). - Record verdicts and sanitized event names only. Never copy raw log lines, paths, account names, e-mail addresses or identifiers into Git, the chat or a commit.
Steps
- Installed version.
Get-AppxPackage -Name AiUsage.DevgivesVersionandPackageFamilyName. Map the version to its source with a read-onlygh api repos/rozputnii/ai-usage-app/releases/tags/preview-<version> --jq .target_commitish, then confirm withgit merge-base --is-ancestor <feature commit> <source>that each pending item's merge is included. An item whose merge is not included stays pending. - Logs. Read only
application-*.jsonlandcritical-*.jsonlunder%LOCALAPPDATA%\Packages\<PackageFamilyName>\LocalState\logs, from the update time on. Count events byeventIdandseverity. Look for the item's expected outcomes and for failures (critical-*files, repeated warnings,PreviousExitUnknown,LoggerHealthdrops). The reading guide is docs/workflow/logging.md. - Owner observations. For checks that need the owner's eyes or signed-in accounts, list them in one question and record the owner's answers as "owner-reported PASS (date)" or FAIL with the owner's words summarized.
- Record. For each item in the backlog's "Pending owner checks" list: PASS (log evidence or owner-reported), FAIL, or still NOT_RUN, with the installed version and the date. Move PASS items into the feature's verification record (one line in its AC table or Not run table) and delete them from the list. A FAIL becomes a backlog bug item the owner selects.
- Commit the record changes under the Git flow; this is a T0 docs change.
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.