Problem
What problem this solves
Project upkeep spreads across bugs, dependencies, docs, checks, audits, migrations, fixes, verification, and shipping, so maintenance can stall as a list of disconnected commands.
Skill Detail
Run project maintenance from triage through delegated fixes, verification, and ship routing.
A master maintenance lifecycle skill for reviewing project health, creating or continuing specs when needed, delegating remediation, verifying results, and routing ship or deploy.
Problem
Project upkeep spreads across bugs, dependencies, docs, checks, audits, migrations, fixes, verification, and shipping, so maintenance can stall as a list of disconnected commands.
Outcome
You get a master maintenance run that triages, specs when needed, delegates bounded work, verifies, and routes ship or deploy.
Why It Matters
This skill is the recurring maintenance pilot. It turns drift into handled work instead of another backlog report.
Arguments
These are the argument switches documented for this skill. For the general rule behind skill arguments, read the skill modes tutorial.
no argument / fullRuns the master maintenance lifecycle for the current project.
Carries maintenance through spec/readiness when needed, delegated execution, verification, and ship/deploy routing.
quickRuns read-only maintenance triage for the current project.
Keeps the old report-only behavior when you explicitly want no writes.
securityRuns the security maintenance lifecycle for bug risk, dependency vulnerabilities, secret/config hygiene, auth and permission surfaces, remediation gates, verification, and ship routing.
Uses sg-technical deps and sg-technical audit without inventing a separate security audit.
deps / docs / auditsFocuses the maintenance lifecycle on one owner lane.
Still verifies and routes ship when the lane changes the project.
no-shipRuns through verification but stops before sg-ship or sg-deploy.
Returns a ship-ready or blocked report instead of releasing.
globalBuilds a workspace maintenance dashboard from the project registry.
Asks which projects to inspect before doing heavier work.
Related Skills
Run a bug from report to dossier, fix, retest, verification, and ship risk without skipping gates.
A professional bug loop executor that reads bug state and continues through the right ShipGlows owner skills when safe.
Open skill pageUse one explicit technical mode for code risk, dependencies, performance, or a breaking migration.
A unified technical entrypoint with four bounded modes and evidence limits that match the work.
Open skill pageCreate or repair documentation so the repo stays navigable for both humans and agents.
A documentation skill for maintaining docs, metadata, and governance-layout compliance across project surfaces.
Open skill pageRun the standard technical checks and fix the obvious issues before you pretend the work is done.
A practical quality gate for typecheck, lint, build, and related technical validation in the current project.
Open skill pageRun a broad project audit when you need a high-level map of what is weak before you decide what to fix.
The top-level audit skill scans across multiple quality domains so you can see where the real risk or drift sits.
Open skill pageKeep the task list coherent after work moves, instead of letting tracking fall behind reality.
A task-management skill for updating `TASKS.md`, reflecting progress, and capturing the next sensible steps.
Open skill pageTriage a bug fast, decide whether it is safe to patch now, and route it correctly.
The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.
Open skill pageRun non-trivial work from story to spec, build, verification, closeout, and ship without making the user drive every gate.
The master user-facing lifecycle orchestrator for carrying a story, bug, or goal through ShipGlows's spec, readiness, implementation, verification, onboarding consideration, documentation, closure, and shipping gates.
Open skill pageRun the whole release confidence loop instead of stitching checks, ship, prod, browser proof, and verification by hand.
A release orchestration skill for moving work through technical checks, bounded shipping, deployment readiness, post-deploy evidence, final verification, and optional changelog routing.
Open skill pageCommit and push quickly when the work is actually ready, instead of stretching closure into another vague step.
A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
Open skill pageGo Deeper
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.