change-checklist

Mandatory pre-ship verification before calling end_change(). Covers Phase 0 survey, test, multi-OS, multi-role, docs, final verification, and reflexion. Every governance cycle must run this before closing.

Ir a la instalación

Repositorio: lukemcqueen/hermes-cortex
Última actividad en el origen: 1 de septiembre de 2026 a las 06:17
Idioma detectado de SKILL.md: inglés
Estrellas: 4
Forks: 1

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/lukemcqueen/hermes-cortex --skill change-checklist

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

8 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

agent-health-monitoring

Cross-server agent health monitoring using binary status vectors — deploy health endpoints on each agent, poll from orchestrator, alert on state transitions.

2026-09-01

langfuse-observability

Wire a self-hosted Langfuse instance to Hermes Agent — generate API keys, configure env vars, enable the bundled plugin, install SDK, and verify traces flow.

2026-09-01

enforcement-change-safety

Use before enforcement code changes or shared-repo commits.

2026-09-01

Ver todos los de este repositorio

name	change-checklist
version	2.1.0
category	software-development
description	Mandatory pre-ship verification before calling end_change(). Covers Phase 0 survey, test, multi-OS, multi-role, docs, final verification, and reflexion. Every governance cycle must run this before closing.
author	Hermes Cortex
license	MIT
platforms	["linux","macos"]
metadata	{"hermes":{"tags":["governance","testing","documentation","multi-os","multi-role","quality"],"related_skills":["loop-governance","change-test-loop","two-hard-rules","cron-job-management","survey-before-action","agent-contract"]}}

Change Checklist — Pre-Ship Validation

The Workmanship Principle

Before the checklist: every change you ship is a reflection of your workmanship. Do not stop at the obvious path. The easy path — changing one file, running one test — is never the complete path. For every change, ask:

What else does this touch? Configs, docs, other agents, deployed state?
Did I verify the SYMPTOM resolves (not just the code path)?
Did I check sibling locations for the same flaw?
Did I run the doctor to see if my change broke something else?
Did I push changes so the whole fleet benefits?

Agents that ship incomplete work erode trust. The checklist below is the minimum — your judgment determines when the work is genuinely done.

Writing quality for prompts, docs, and skills

When creating or updating cron prompts, command output examples, or skill content in this session, apply these two principles:

Concrete examples, never abstract placeholders. Show real-looking values (43 cycles scored, $0.006/run, 2026-07-15 10:01 KST), not annotated templates ([N] cycles, <cost>, <datetime>). LLMs mimic concrete structure faithfully; they interpret placeholders loosely.
Be concise — every sentence must earn its place. If a sentence doesn't change agent behavior, it's token waste. After writing, review: "Would the agent do anything differently if I deleted this?" If no, delete it.

When to Load This Skill

Load this skill before calling end_change() on any change that:

Modifies scripts (.sh, .py, .rb, .js)
Changes deploy configs (nginx, systemd, launchd)
Adds/modifies crons
Updates docs that other agents consume
Changes cortex-update.sh or install-crons.sh

Phase 0b: Load Domain Skills (Before begin_change)

Run survey-before-action Phase 0a before opening a governance lock. The full operation-type × file-extension domain-skill mapping table lives there (survey-before-action is always-loaded, so it is already in context). Load every matching skill, run skills_list(category=<domain>) for discovery, and load any referenced — a skill isn't loaded until you've read its content via .

Anti-pattern	Why it's wrong
"I tested it manually"	Manual = ad-hoc, not repeatable, no proof. Run the actual tool. Also: manual `python3 script.py` doesn't update the cron scheduler's `last_status` — the doctor reads scheduler status, not script exit code.
"It's just a health check message — agents won't see it"	Agent-facing messages are instructions. A WARN saying "bus daemon not running" makes agents try to install one. All output is visible to all agents — gate or rephrase accordingly.
"I already did the main work, the rest is trivial"	The omitted work (docs, deploy, doctor, push) is where trust breaks. The work isn't done until it's ALL done.
"Other OS can wait"	It won't. Ship OS-agnostic on day one.
"Docs can come later"	Later = never. Update docs before end_change().
"Titus doesn't need this"	If it runs on Titus, it must be tested there. Push-only ≠ skip.
"The hook didn't catch it"	The hook is syntax-level. You catch semantics here.
"sudo nginx -t failed"	Don't ship broken syntax. Fix and re-verify.
"I'll write a migration script"	The git commit that deletes orphan files IS the migration. A separate script is only needed if the cleanup requires conditional logic across machines. If the commit can do it, ship the commit — not a script nobody will run.
"I'll test with a long sleep"	Blind-sleeping 60-90s wastes time when you could poll every 15s and detect completion sooner. Use periodic short-interval polling (`time.sleep(15)` max in a loop up to 8 tries) instead of one long `sleep(90)`. The terminal has a 60s timeout — Python `time.sleep()` loops inside a single terminal command count against the same timeout, so keep each iteration fast. Prefer running checks as separate rapid terminal calls.
"It worked from my repo terminal"	A script that works from `~/hermes-cortex/` can fail from the deployed path due to different cwd, env vars, or file resolution. Always test from the actual cron runtime path (`~/.hermes/scripts/`), not just the repo source. `Path(\"\")` from an unset env var is the classic trap — works in a session with the var set, crashes in cron.

Purpose	Linux	macOS (arm64)	macOS (x86_64)
nginx config dir	`/etc/nginx`	`/opt/homebrew/etc/nginx`	`/usr/local/etc/nginx`
nginx sites dir	`sites-available/`	`servers/`	`servers/`
nginx sites-enabled	`sites-enabled/`	`servers/` (same as avail)	`servers/`
htpasswd file	`.hermes-htpasswd`	`.htpasswd`	`.htpasswd`
nginx log dir	`/var/log/nginx`	`/opt/homebrew/var/log/nginx`	`/usr/local/var/log/nginx`
Service manager	`systemctl --user`	`launchctl`	`launchctl`
Package manager	`apt` / `yum` / `dnf`	`brew`	`brew`

change-checklist

Opciones de instalación

Revisa los archivos de origen

Change Checklist — Pre-Ship Validation

The Workmanship Principle

Writing quality for prompts, docs, and skills

When to Load This Skill

Phase 0b: Load Domain Skills (Before begin_change)

Change Checklist — Pre-Ship Validation

The Workmanship Principle

Writing quality for prompts, docs, and skills

When to Load This Skill

Phase 0b: Load Domain Skills (Before begin_change)

Phase 0: Survey the Change Surface

The Checklist

Phase 1: Test the Change

Phase 1.5: Adversarial Verification (MANDATORY — no bypass)

Phase 2: Verify Multi-OS Compatibility

Phase 3: Verify Multi-Role Compatibility

Role-Aware Health Check Patterns

Phase 4: Update Documentation

Phase 5: Final Verification

Phase 6: Reflexion (Self-Critique)

Anti-Patterns to Avoid

Quick Reference: Path Patterns by OS

change-checklist

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Change Checklist — Pre-Ship Validation

The Workmanship Principle

Writing quality for prompts, docs, and skills

When to Load This Skill

Phase 0b: Load Domain Skills (Before begin_change)

Más de este repositorio

Change Checklist — Pre-Ship Validation

The Workmanship Principle

Writing quality for prompts, docs, and skills

When to Load This Skill

Phase 0b: Load Domain Skills (Before begin_change)

Phase 0: Survey the Change Surface

The Checklist

Phase 1: Test the Change

Phase 1.5: Adversarial Verification (MANDATORY — no bypass)

Phase 2: Verify Multi-OS Compatibility

Phase 3: Verify Multi-Role Compatibility

Role-Aware Health Check Patterns

Phase 4: Update Documentation

Phase 5: Final Verification

Phase 6: Reflexion (Self-Critique)

Anti-Patterns to Avoid

Quick Reference: Path Patterns by OS