SkillAgentSearch skills...

deepchat-sdd-cleanup

Use only when a developer explicitly asks to clean, prune, tidy, or organize DeepChat SDD documentation after implementation and validation.

Install / Use

npx skills add ThinkInAIXYZ/deepchat --skill deepchat-sdd-cleanup

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of deepchat-sdd-cleanup

deepchat-sdd-cleanup scores 83/100 on our quality scale, 903rd of 1,155 Content & Media skills we index.

Its SKILL.md is 3.1 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 6,372 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
15/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 27 days ago, so deepchat-sdd-cleanup is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-02. Automated pattern scan on 2026-10-02. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

deepchat-sdd-cleanup compared with similar skills

All 4 of these similar skills score higher than deepchat-sdd-cleanup; compare them before choosing.

SkillScoreStarsUpdatedFormat
deepchat-sdd-cleanup (this skill)by ThinkInAIXYZ836.4k27d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install deepchat-sdd-cleanup?
Run npx skills add ThinkInAIXYZ/deepchat --skill deepchat-sdd-cleanup. The install tabs above show the steps for each supported agent.
Which AI agents does deepchat-sdd-cleanup work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is deepchat-sdd-cleanup safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is deepchat-sdd-cleanup still maintained?
The repository was last updated 27 days ago, so deepchat-sdd-cleanup is actively maintained.

name: deepchat-sdd-cleanup description: Use only when a developer explicitly asks to clean, prune, tidy, or organize DeepChat SDD documentation after implementation and validation. Scans docs/features, docs/issues, and docs/architecture; prefers multi-agent review when available; removes completed issue docs when a linked GitHub issue is closed or implementation and validation evidence proves the bug no longer exists, drops stale plans and legacy task files from completed feature or architecture goals, and deletes obsolete feature or architecture docs.

DeepChat SDD Cleanup

Rule

Run this skill only when the developer explicitly asks for SDD cleanup, documentation tidying, pruning, or removal of completed/stale SDD files. Do not run it as an automatic final step of ordinary feature, bug, architecture, or release work.

Workflow

  1. Inspect docs/spec-driven-dev.md, docs/README.md, and git status.
  2. Inventory docs/features, docs/issues, and docs/architecture with find or rg.
  3. Prefer parallel sub-agent review when available:
    • one pass for docs/features
    • one pass for docs/issues
    • one pass for docs/architecture
    • optional verifier pass over proposed deletes
  4. Apply only changes with clear evidence. Keep a concise keep/delete/update list for handoff.
  5. Validate references after edits.

Cleanup Rules

  • Completed feature or architecture goal: delete plan.md and any legacy tasks.md; keep spec.md only when it still defines a maintained contract, regression guard, platform policy, or architecture decision.
  • Completed issue goal: delete the issue folder when a linked GitHub issue is closed or the implementation and validation evidence prove the bug no longer exists.
  • Removed feature: delete its folder when the product/code path is gone and the spec has no reusable decision record.
  • Obsolete architecture: delete its folder when the module was fully replaced and the doc no longer describes a maintained boundary; otherwise update the spec.
  • Historical feature spec affected by an architecture refactor: update the retained spec instead of leaving contradictory docs.

GitHub Checks

Use gh only when it is installed and authenticated. For linked issue docs, verify closure with gh issue view <number> --json state,url,title when possible. If gh is unavailable, do not delete solely because a GitHub link looks old.

Never Delete

  • Active work with unchecked plan.md steps or legacy tasks.
  • Any document containing unresolved [NEEDS CLARIFICATION].
  • A document referenced by docs/README.md, docs/ARCHITECTURE.md, docs/FLOWS.md, or AGENTS instructions unless the reference is updated in the same change.
  • Runtime baselines or machine-read files unless the cleanup request explicitly covers them.

Validation

  • Run rg -n "plan.md|tasks.md|docs/archives|NEEDS CLARIFICATION" docs AGENTS.md .agents/skills and inspect any stale policy references.
  • Run git status --short.
  • For Markdown-only cleanup, formatting/lint commands are optional unless repository instructions or touched generated files require them.

Related Skills

View on GitHub
GitHub Stars6.4k
CategoryContent
Updated27d ago
Forks758

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions