SkillsAdd

kw12121212/auto-spec-driven

spec-driven-maintenance

Inspect or run the manual maintenance workflow. Uses explicitly configured repository checks, applies safe auto-fixes, and archives successful maintenance changes.

First seen Mar 30, 2026

Installation

$ npx skills add kw12121212/auto-spec-driven --skill spec-driven-maintenance
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from kw12121212/auto-spec-driven · top by installs.

npx skills add kw12121212/auto-spec-driven
spec-driven-auto 41 spec-driven-brainstorm 41 spec-driven-review 40 spec-driven-init 40 spec-driven-apply 40 spec-driven-propose 39 spec-driven-verify 39 spec-driven-modify 38 spec-driven-cancel 38 spec-driven-archive 38

Browse all from kw12121212/auto-spec-driven

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
More metadata
skill_id
spec_driven_maintenance
author
auto-spec-driven
type
agent_skill
version
1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,296 B
  • docs SUMMARY.md 194 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 36 installs

SKILL.md

You are helping the user manage the manual maintenance workflow.

This Skill's Commands

If you cannot remember the exact command used by this skill, look it up here before running anything. Do not guess.

run-maintenance: node {{SKILL_DIR}}/scripts/spec-driven.js run-maintenance [path]

Prerequisites

The target project must already contain .spec-driven/ at the project root. Before proceeding, verify:

ls .spec-driven/

If this fails, run /spec-driven-init first.

Steps

  1. Choose the maintenance action:

- Run the maintenance workflow manually right now - Inspect or adjust the maintenance config

  1. Read existing maintenance assets when present:

- .spec-driven/maintenance/config.json - Relevant README or project docs that define lint/test/typecheck commands

  1. For a manual maintenance run — run:

`` node {{SKILL_DIR}}/scripts/spec-driven.js run-maintenance [path] `` Then report whether the run: - failed because the maintenance config is missing or invalid - skipped because the repo was dirty, had no configured checks, or already had an active maintenance change - completed cleanly because all configured checks already passed - found unfixable failures - became blocked during fix, archive, commit, or branch-restore work - created a maintenance branch/change and repaired the configured checks

  1. When editing config:

- Keep checks limited to commands the repo explicitly supports - Only add fixCommand for deterministic, low-risk repairs - Use changePrefix, branchPrefix, and commitMessagePrefix only when the repo needs custom naming

Rules

  • Do not add speculative fixCommand entries for semantically ambiguous test failures
  • Treat the maintenance config as the source of truth for allowed maintenance fixes
  • If a maintenance run leaves a blocked change behind, report that clearly instead of pretending the repair succeeded