Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

freed-ship-www

Sterne7

Forks1

Aktualisiert13. Juli 2026 um 20:41

Publish verified Freed marketing changes from www, refresh the public changelog after a release, or apply an approved structured roadmap update. Use for production freed.wtf deployments. Require explicit deployment authority, exact commit and deployment identity, and source-attributed roadmap data. Never fast-forward www to dev.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

freed-project

freed-project/freed

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

2 Dateien

SKILL.md

readonly

name	freed-ship-www
description	Publish verified Freed marketing changes from www, refresh the public changelog after a release, or apply an approved structured roadmap update. Use for production freed.wtf deployments. Require explicit deployment authority, exact commit and deployment identity, and source-attributed roadmap data. Never fast-forward www to dev.
disable-model-invocation	true

Ship WWW

Deploy only reviewed state from www and prove which commit produced the live site.

Safety contract

Record the task ID, granted deployment authority, source branch, exact commit SHA, and expected public change.
Require a clean www checkout whose SHA matches the reviewed PR or approved deployment request.
Never merge or fast-forward www to dev. Sync approved product-owned files from main only when the requested mode requires it.
Use repository Vercel helpers so every command retains the required aubreyfs-projects scope. Never run raw Vercel commands from the repository root.

Modes

Ship current or merged WWW

Confirm the requested SHA is present on origin/www and required checks passed for that SHA.
Run the website build from website/.
Run ./scripts/vercel-deploy-production.sh website only with explicit deployment authority.

Refresh changelog

Require the published release ID, tag, channel, source SHA, and approved release-note artifact.
Update the static changelog from current www without merging dev.
Build, deploy, and verify the release appears on the production URL.

Publish roadmap status

Require the approved source commit and digest for docs/roadmap-status.json.
Run node scripts/validate-roadmap-status.mjs against the source data.
Confirm website/src/app/roadmap/RoadmapContent.tsx matches the manifest exactly. Do not infer status from phase prose.
Build and deploy from www. Do not combine this with unrelated product promotion.

Close out

Record the deployed www SHA, Vercel deployment ID, deployment time, production URL, build result, and source release or roadmap identity. Verify the production response belongs to the new deployment. An old healthy URL is not evidence that the requested commit shipped.

Mehr aus diesem Repository

gleiches Repository

freed-build-feature

freed-project/freed

Build governed Freed product work in a worktree based on origin/dev, verify the runnable slice, and publish a correctly staged pull request to dev. Use for Desktop, PWA, shared packages, sync, capture, release tooling, product behavior, and product documentation. Also use for stability tasks that require a stable task identity, a measurable counter, native validation, or an installed-build verification handoff. Do not use for public website work targeting www.

2026-07-247

freed-ship-build

freed-project/freed

Ship and verify a versioned Freed Desktop build through GitHub Actions. Use when asked to cut a dev or production release, publish a reviewed build, or repair a failed release pipeline. Preserve source and installed build identity, require exact-head validation including native tests, and create a governed post-install verification task.

2026-07-247

freed-stability-controller

freed-project/freed

Reconcile Freed stability observations, tasks, approvals, releases, soaks, and outcomes into one governed lifecycle. Use when coordinating the continuous background agents, deduplicating repeated findings, selecting the next stability action, advancing task state, or deciding that no fresh actionable work exists. This skill coordinates authority and handoffs but does not implement product code.

2026-07-247

freed-triage

freed-project/freed

Reconcile fresh Freed stability evidence into governed, deduplicated GitHub debt issues. Use after runtime alarms, soak verdicts, canary results, or CI failures, and when deciding what to fix next. Require healthy evidence sources, temporal and build matching, issue identity, atomic evidence generations, explicit authority, and instrumentation-first handling of contradictory metrics.

2026-07-247

freed-soak

freed-project/freed

Run and judge an installed-build soak of Freed Desktop from terminal evidence. Use for release observation, overnight stability windows, or post-change verification. Require the canonical release-verifier lease, the exclusive collector session lock, event-derived build identity, immutable time bounds, source-health checks, comparable process generations, and explicit inconclusive results when identity or coverage is insufficient.

2026-07-227

freed-provider-risk-review

freed-project/freed

Prepare and verify both owner gates for any Freed change that could alter behavior visible to X, Facebook, Instagram, LinkedIn, or another provider. Use before implementation that changes WebView loads, navigation, requests, retries, cadence, cookies, headers, scrolling, clicking, extraction scripts, media loading, login behavior, or provider timing, and again before making the pull request ready. Preparing a review never grants approval.

2026-07-167

name	freed-ship-www
description	Publish verified Freed marketing changes from www, refresh the public changelog after a release, or apply an approved structured roadmap update. Use for production freed.wtf deployments. Require explicit deployment authority, exact commit and deployment identity, and source-attributed roadmap data. Never fast-forward www to dev.
disable-model-invocation	true

Ship WWW

Deploy only reviewed state from www and prove which commit produced the live site.

Safety contract

Record the task ID, granted deployment authority, source branch, exact commit SHA, and expected public change.
Require a clean www checkout whose SHA matches the reviewed PR or approved deployment request.
Never merge or fast-forward www to dev. Sync approved product-owned files from main only when the requested mode requires it.
Use repository Vercel helpers so every command retains the required aubreyfs-projects scope. Never run raw Vercel commands from the repository root.

Modes

Ship current or merged WWW

Confirm the requested SHA is present on origin/www and required checks passed for that SHA.
Run the website build from website/.
Run ./scripts/vercel-deploy-production.sh website only with explicit deployment authority.

Refresh changelog

Require the published release ID, tag, channel, source SHA, and approved release-note artifact.
Update the static changelog from current www without merging dev.
Build, deploy, and verify the release appears on the production URL.

Publish roadmap status

Require the approved source commit and digest for docs/roadmap-status.json.
Run node scripts/validate-roadmap-status.mjs against the source data.
Confirm website/src/app/roadmap/RoadmapContent.tsx matches the manifest exactly. Do not infer status from phase prose.
Build and deploy from www. Do not combine this with unrelated product promotion.