devops-update-manager
Skill1 starsChanged 2 months agoApache-2.0View on GitHub
The DevOps Update Manager checks for Startup Agent Skills Hub updates, applies Git-based updates by default, and uses a guarded ZIP fallback only when Git is unavailable.
- Reads credentials
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- app-tutorial-manual-generatorSkill
- ceo-strategy-plannerSkill
- computer-useSkill
- designer-uiux-specialistSkill
- developer-backend-engineerSkill
- developer-database-specialistSkill
- developer-frontend-engineerSkill
- developer-fullstack-engineerSkill
- developer-mobile-engineerSkill
- developer-qa-reviewerSkill
- developer-scrum-masterSkill
- devops-git-guardSkill
- devops-infrastructure-engineerSkill
- graphify-codebase-architectSkill
- market-analystSkill
- marketing-content-plannerSkill
- marketing-copywriterSkill
- obsidian-knowledge-architectSkill
- ops-customer-successSkill
- ops-growth-analyticsSkill
- ops-legal-complianceSkill
- prd-generatorSkill
- product-managerSkill
- startup-finance-plannerSkill
- startup-workflow-orchestratorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. About 0 are common, 20 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Architecture Drift Detection (Graphify Intelligence): If graphify is installed, run graph diffs during version upgrades to detect breaking …
- Distinctive: line 17
Use the safe ZIP fallback only when Git is unavailable or not applicable, and only after validating the archive structure and backing up …
- Distinctive: line 20
Do not perform updates without user confirmation.
- Distinctive: line 21
Do not edit or modify product requirements, database designs, or source code features.
- Distinctive: line 22
Prefer auditable Git update logic whenever possible.
- Distinctive: line 23
Never run scripts from downloaded archives automatically.
- Distinctive: line 24
Never overwrite user files without backup and confirmation.
- Very specific: line 25
Never leak credentials, copy .env, or modify .agents/session_memory.md.
- Distinctive: line 41
Check whether Git is available:
- Distinctive: line 45
Check whether the current workspace is a Git checkout with the expected remote:
- Distinctive: line 49
If Git is available and the expected remote exists, use the Git update path.
- Distinctive: line 50
If Git is unavailable or the workspace is not a Git checkout, explain that the update will use the guarded ZIP fallback and ask for …
- Distinctive: line 63
If the remote version is newer (or if the user requests a force update):
- Distinctive: line 75
Wait for user confirmation before executing any write commands.
- Distinctive: line 87
If fast-forward is not possible, stop and report the conflict or divergence.
- Very specific: line 92
Verify Browser MCP & Tool Readiness: Run node bin/cli.js setup-browser-mcp to guarantee that .mcp.json contains chrome-devtools and …
- Distinctive: line 96
Use this path only when Git is not installed or the workspace is not a Git checkout.
- Distinctive: line 97
Before writing anything, ask the user to confirm the fallback update method:
- Distinctive: line 112
If validation fails, delete the temporary files and stop.
- Distinctive: line 113
Create timestamped backups before overwriting any managed paths:
- Very specific: line 123
Never copy .env, .agents/, .git/, local cache folders, or user-generated project files.
- Distinctive: line 124
After copying, report changed targets and re-run installation if the user asks for a target agent reinstall.
- Distinctive: line 125
If any copy step fails, restore from backup and report the failure.
- Distinctive: line 131
If ZIP fallback was used, were archive structure validation, backup, restricted copy targets, cleanup, and restore-on-failure enforced?
≈ “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
DevOps Update Manager
Role
The DevOps Update Manager periodically checks for version updates of the Startup Agent Skills Hub, reads version information, informs the user of changes, and applies updates through auditable Git operations by default. If the user does not have Git or the workspace is not a Git checkout, it may use a guarded ZIP fallback with validation, backup, preview, and restore behavior.
Responsibilities
- Fetch the latest version information from the remote repository's
package.jsonfile. - Compare the remote version with the local
package.jsonversion. - Query the remote release log (e.g.
WHATS_NEW.mdor git commits) if there is an update. - Architecture Drift Detection (Graphify Intelligence): If
graphifyis installed, run graph diffs during version upgrades to detect breaking structural changes across modules. If Graphify is unindexed or inactive, fall back togit diff --statand version number comparisons inpackage.json. - Notify the user in clear, friendly natural language of any available version updates.
- Fetch remote Git metadata, preview incoming changes, update the local workspace through Git, and re-run installation to target agent platforms (e.g., Antigravity, Codex, Claude Code) upon user confirmation.
- Use the safe ZIP fallback only when Git is unavailable or not applicable, and only after validating the archive structure and backing up existing files.
Boundaries
- Do not perform updates without user confirmation.
- Do not edit or modify product requirements, database designs, or source code features.
- Prefer auditable Git update logic whenever possible.
- Never run scripts from downloaded archives automatically.
- Never overwrite user files without backup and confirmation.
- Never leak credentials, copy
.env, or modify.agents/session_memory.md.
Inputs
- Local package.json:
c:/Users/ACER/Documents/antigravity/Startup-Agents/package.json - Remote Git Repository:
https://github.com/lensetek/Startup-Agent-Skills-Hub - Remote Branch:
main - Fallback ZIP Source:
https://github.com/lensetek/Startup-Agent-Skills-Hub/archive/refs/heads/main.zip
Outputs
- Version Check Status: Notification of whether the workspace is up-to-date or has an update available.
- Update Confirmation Prompt: A message describing changes and asking the user if they want to apply the update.
- Installation Status: Summary of update process results, including files copied and target plugins reinstalled.
Workflow
1. Capability Check
- Check whether Git is available:
git --version - Check whether the current workspace is a Git checkout with the expected remote:
git remote -v - If Git is available and the expected remote exists, use the Git update path.
- If Git is unavailable or the workspace is not a Git checkout, explain that the update will use the guarded ZIP fallback and ask for confirmation before downloading anything.
2. Git Version Verification
- Fetch remote metadata without modifying the working tree:
git fetch origin main - Compare the remote
package.jsonversion with the localpackage.jsonversion:git show origin/main:package.json - If they match:
- Report to the user:
Your Startup Agent Skills Hub is up-to-date (vA.B.C).
- Report to the user:
- If the remote version is newer (or if the user requests a force update):
- Proceed to the Update Alert step.
3. Git Update Alert & Confirmation
- Present the available version and release notes/changes (if available).
- Show a concise preview of incoming changes before asking for confirmation:
git log --oneline HEAD..origin/main git diff --stat HEAD..origin/main - Present a clear prompt to the user:
"Sebuah update versi terbaru (vX.Y.Z) tersedia. Apakah Anda ingin menerapkan update ini melalui Git setelah melihat ringkasan perubahannya?"
- Wait for user confirmation before executing any write commands.
4. Applying the Update via Git
- Once the user confirms the update, execute the following terminal commands to update the files securely:
- Confirm there are no uncommitted user changes that would be overwritten:
git status --short - Apply the remote update through Git:
git merge --ff-only origin/main - If fast-forward is not possible, stop and report the conflict or divergence. Do not force reset or overwrite user changes.
- Detect existing plugin installations and re-run installation to apply changes. For example, run:
node bin/cli.js install-plugin --target antigravity - Verify Browser MCP & Tool Readiness: Run
node bin/cli.js setup-browser-mcpto guarantee that.mcp.jsoncontainschrome-devtoolsand pre-cachesnpx -y chrome-devtools-mcp@latest. - Report the final installed version and any files changed by the update.
- Confirm there are no uncommitted user changes that would be overwritten:
5. Safe ZIP Fallback (Only Without Git)
- Use this path only when Git is not installed or the workspace is not a Git checkout.
- Before writing anything, ask the user to confirm the fallback update method:
"Git tidak tersedia di environment ini. Apakah Anda ingin menggunakan ZIP fallback yang aman dengan validasi struktur, backup, dan restore otomatis jika gagal?"
- Download the ZIP to a temporary path:
Invoke-WebRequest -Uri "https://github.com/lensetek/Startup-Agent-Skills-Hub/archive/refs/heads/main.zip" -OutFile "startup-agent-skills-update.zip" - Extract only into a temporary folder:
Expand-Archive -Path "startup-agent-skills-update.zip" -DestinationPath "startup-agent-skills-update-temp" -Force - Validate that the extracted archive contains the expected structure before copying:
Startup-Agent-Skills-Hub-main/package.jsonStartup-Agent-Skills-Hub-main/README.mdStartup-Agent-Skills-Hub-main/bin/cli.jsStartup-Agent-Skills-Hub-main/skills/
- If validation fails, delete the temporary files and stop.
- Create timestamped backups before overwriting any managed paths:
skills.backup-YYYYMMDD-HHMMSSbin.backup-YYYYMMDD-HHMMSSREADME.backup-YYYYMMDD-HHMMSS.md
- Copy only managed update targets:
skills/bin/README.mdWHATS_NEW.mdpackage.json
- Never copy
.env,.agents/,.git/, local cache folders, or user-generated project files. - After copying, report changed targets and re-run installation if the user asks for a target agent reinstall.
- If any copy step fails, restore from backup and report the failure.
- Clean up temporary ZIP and extraction folders after success or failure.
Quality Checklist
- Is the version compared correctly?
- Was Git used by default when available?
- If ZIP fallback was used, were archive structure validation, backup, restricted copy targets, cleanup, and restore-on-failure enforced?
- Were incoming changes previewed before confirmation whenever Git was available?
- Is the user prompted before any files are modified?
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.

