publish-site-canary

Étoiles0

Forks0

Mis à jour25 juin 2026 à 16:25

Publish a single McCormick brand site to a canary publishing target for staged verification before going wide.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

smithdak

smithdak/sleuth

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	publish-site-canary
description	Publish a single McCormick brand site to a canary publishing target for staged verification before going wide.

Publish site

Steps:

Confirm the build is green and the Helix check passed.
Run a smart publish of the site to the Preview publishing target.
Publish related media items referenced by the site.
Verify the published item count matches the source database.
Record the publish in the deploy log with a timestamp.

Plus depuis ce dépôt

même dépôt

code-check

smithdak/sleuth

Reviews Sitecore code for layer issues.

2026-06-250

helix-layer-check

smithdak/sleuth

Use when reviewing or adding Sitecore C# code to enforce Helix architecture layer boundaries — Foundation, Feature, and Project dependency direction. Trigger before committing Sitecore solution code, or whenever a new project reference is introduced.

2026-06-250

publish-site

smithdak/sleuth

Publish a single McCormick brand site to the Internet publishing target after a successful build and Helix check.

2026-06-250

qa-smoke-check

smithdak/sleuth

Run the post-deploy smoke suite against the McCormick QA environment and report failures grouped by brand site.

2026-06-250

serialization-audit

smithdak/sleuth

Helps with serialization stuff.

2026-06-250

sleuth

smithdak/sleuth

Use to investigate, audit, or reverse-engineer an unfamiliar or organically-grown Claude Code system (a .claude tree, an agent harness, a teammate's or client's setup) before trusting, extending, or rebuilding it. Trigger on "audit this harness", "what's actually in this .claude setup", "archaeology on this repo", "what's load-bearing / dead / dangerous here", "do recon before I rebuild", or when a discovery/inventory pass over agent infrastructure is needed. Produces a ranked, evidence-linked System Dossier, not a flat inventory.

2026-06-250

Exécutez n'importe quel Skill en un clic