Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

aiws-sdd-code-maintenance

Étoiles2

Forks0

Mis à jour22 juin 2026 à 19:05

Propagate a REASONS spec change into existing code — diff old vs active spec, classify each change, apply with per-change confirmation. Trigger: code must follow an edited spec.

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

grojof

grojof/ai-workspace-generator

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

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	aiws-sdd-code-maintenance
description	Propagate a REASONS spec change into existing code — diff old vs active spec, classify each change, apply with per-change confirmation. Trigger: code must follow an edited spec.
license	Apache-2.0
metadata	{"author":"ai-workspace","version":"1.0"}

aiws-sdd-code-maintenance — propagate spec changes into code

When a spec changes, bring the code back in sync. Diff the previous spec revision (Git history) against the active spec in {{paths.specs}}/, classify each entity/operation/dependency/flag delta as add / modify / remove, and apply it with per-change confirmation.

Rules

Removals are archived (Git history + change-folder), never silently deleted.
Hand-edited files are detected via SHA-256 vs the recorded hash; never overwrite without confirmation.
Reuse aiws-sdd-code-generation's patterns for the add/modify cases; keep the layer ordering.
When an operation signature changes, hand off to aiws-sdd-test-generation to re-derive its tests.

Record

Append the change set (per-change verdict, files + SHA-256) to {{paths.changes}}/<change>/. The spec stays the source of truth — if the code and spec disagree, fix the spec first.

Plus depuis ce dépôt

même dépôt

aiws-audit

grojof/ai-workspace-generator

Produce a prioritized, read-only audit of the workspace's health and coherence (code, docs, integrity, standards) as a dated report. Use periodically or after big changes to surface what to improve. Read-only — it reports and recommends, never fixes.

2026-06-232

aiws-configure-workspace

grojof/ai-workspace-generator

Configure or re-configure this AI workspace: analyze an existing repo (or set up a new one) and propose a workspace.config.yaml + skill set. Trigger: when the user wants to set up, configure, or re-detect the workspace.

2026-06-232

aiws-dependency-upgrade

grojof/ai-workspace-generator

Assess feasibility and security of version bumps/migrations before touching anything. Trigger: when asked to update dependencies, migrate, or resolve version conflicts.

2026-06-232

aiws-living-docs

grojof/ai-workspace-generator

Keep the living docs (project status) current so the AI always has fresh project context. Trigger: after finishing a task or when project state changed.

2026-06-232

aiws-sdd-apply

grojof/ai-workspace-generator

Implement the tasks in order, keeping the code aligned with the spec and design, checking each off as it lands. Use to execute an agreed plan — if reality diverges from the spec, stop and update the spec first.

2026-06-232

aiws-sdd-archive

grojof/ai-workspace-generator

Fold a verified change's delta into the stable specs and move its folder to the archive. Use only after verify passes: ADDED requirements are appended, MODIFIED replace, REMOVED delete; then the change is archived with its full history.

2026-06-232

name	aiws-sdd-code-maintenance
description	Propagate a REASONS spec change into existing code — diff old vs active spec, classify each change, apply with per-change confirmation. Trigger: code must follow an edited spec.
license	Apache-2.0
metadata	{"author":"ai-workspace","version":"1.0"}

aiws-sdd-code-maintenance — propagate spec changes into code

Rules

Removals are archived (Git history + change-folder), never silently deleted.
Hand-edited files are detected via SHA-256 vs the recorded hash; never overwrite without confirmation.
Reuse aiws-sdd-code-generation's patterns for the add/modify cases; keep the layer ordering.
When an operation signature changes, hand off to aiws-sdd-test-generation to re-derive its tests.

Record

Append the change set (per-change verdict, files + SHA-256) to {{paths.changes}}/<change>/. The spec stays the source of truth — if the code and spec disagree, fix the spec first.