AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

10docs

skill-fitclaw-10devrules-10docs · by fitclaw

|

No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-fitclaw-10devrules-10docs

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fitclaw-10devrules-10docs)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of 10docs? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

10docs — Automated Document Governance

One command. One confirmation. Full execution.

Pipeline: SCAN → UPDATE → ORGANIZE → EXECUTE → VERIFY

Preamble (run first)

# Locate 10dev project root
source "${CLAUDE_SKILL_DIR}/../../bin/detect-root.sh" 2>/dev/null || {
  _10DEV_ROOT="$(cd "$(dirname "$0")/../.." 2>/dev/null && pwd)"
  echo "10DEV_ROOT: ${_10DEV_ROOT}"
}

# --- SCAN — collect all data ---
echo "=== SCAN ==="

# Project state
_BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
_HAS_SYNC_CONFIG=$([ -f .10dev/doc-sync.yaml ] && echo "yes" || echo "no")
echo "BRANCH: $_BRANCH | SYNC_CONFIG: $_HAS_SYNC_CONFIG"

# Health audit (state files + governance metrics)
echo "--- health-audit ---"
bash "${_10DEV_ROOT}/bin/doc-health-audit.sh" . 7

# Drift check (broken pointers, undocumented dirs, stale refs, missing docs)
echo "--- drift-check ---"
bash "${_10DEV_ROOT}/bin/doc-drift-check.sh" .

# SOOT check (cross-file duplicates)
echo "--- soot-check ---"
bash "${_10DEV_ROOT}/bin/doc-soot-check.sh" .

# File inventory with line counts and TOC status
echo "--- file-inventory ---"
for f in *.md docs/*.md; do
  [ -f "$f" ] || continue
  bash "${_10DEV_ROOT}/bin/doc-toc-gen.sh" "$f" --check-only
done

# CLAUDE.md size
echo "--- claude-md ---"
[ -f CLAUDE.md ] && wc -l CLAUDE.md

Procedure — MANDATORY STEPS

DO NOT read the router SKILL.md or other files. Everything you need is here. Execute these steps IN ORDER.

Step 1: READ all docs

From scan results, identify every .md file in the project. Read them ALL — CLAUDE.md, README.md, docs/*.md. You need the full picture before making any changes.

Step 2: UPDATE — Fix documentation drift FIRST

Before any cleanup, ensure docs are accurate and complete. Use the drift-check output.

2a. Fix broken pointers — For each broken_pointers entry: the link target doesn't exist. Either:

  • Update the link to point to the correct file (if it was renamed/moved)
  • Remove the link if the target was deleted
  • Create the missing doc if it should exist

2b. Document undocumented directories — For each undocumented_dirs: a source directory exists but no doc mentions it. Add a section to the appropriate doc (ARCHITECTURE.md, README.md, or CLAUDE.md) describing what this directory contains.

2c. Fix stale CLAUDE.md references — For each stale_claude_refs: a file path in CLAUDE.md doesn't exist anymore. Update or remove the reference.

2d. Fix version drift — If readme_version_drift is true: README.md mentions an old version. Update it to match package.json.

2e. Create missing docs — For each missing_docs entry: a standard doc is expected but doesn't exist. Create it with appropriate content based on the codebase.

2f. Update stale docs for changed code — For each stale_doc_dirs: code in this directory changed recently but related docs didn't. Read the code changes and update the relevant docs.

Execute all UPDATE actions immediately — no confirmation needed. These are corrections, not preferences.

Step 3: ORGANIZE — Build the cleanup plan

Now that docs are accurate, classify findings into four categories:

DELETE — Content in CLAUDE.md that also exists in an L2 file.

  • Delete from CLAUDE.md, replace with > See {L2 file}
  • For SOOT duplicates across L2 files: keep in authority, delete from others
  • Authority: docs/state-files.md > docs/{domain}.md > README.md > CLAUDE.md

TOC — Files >200 lines without ## 目录 (from file-inventory).

  • Generate and insert after frontmatter

ARCHIVE — Stale/one-time content.

  • Files: *-plan.md, *-sprint*.md, *-checklist.md, *-recovery*.md
  • CLAUDE.md completed phase sections → compress to 1-line
  • Stale completed tasks in todo.md

EXTRACT — CLAUDE.md blocks that are NOT duplicated, NOT essential for AI context, AND >10 lines.

  • Create docs/{topic}.md, replace with > Details: [topic](docs/{topic}.md)

Step 4: Present ONE consolidated report

Output this EXACT format:

/10docs — DOCUMENT GOVERNANCE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Project: {name} | CLAUDE.md: {N} lines (target: <100)

UPDATED ({N} actions):
  ✏️ {description of each update action taken in Step 2}

DELETE ({N} actions):
  ✂ {description of each delete action}

TOC ({N} files):
  📑 {file} ({N} lines) — insert ## 目录

ARCHIVE ({N} items):
  📦 {description of each archive action}

EXTRACT ({N} blocks):
  📤 {description of each extract action}

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
After: CLAUDE.md ≈ {N} lines | AI Friendliness: {score}/5
Apply cleanup? [Y/n]

UPDATED section shows what was already done (Step 2). The remaining sections need confirmation. If a category has 0 actions, show (0 actions) — do not skip.

Step 5: Execute cleanup on confirmation

On Y or user proceeds, execute in order:

  1. DELETE — remove duplicates, add pointers
  2. EXTRACT — split to new files, add index entries
  3. TOC — generate and insert (including newly created files)
  4. ARCHIVE — git mv files, compress CLAUDE.md sections

Step 6: Verify

Run bin/doc-health-audit.sh again. Output:

DONE: {N}/{M} actions applied
Before → After:
  CLAUDE.md: {N} → {N} lines
  AI Friendliness: {N}/5 → {N}/5

Variant: /10docs audit

Steps 1-4 only. Show report, do NOT execute. End with "Run /10docs to apply."

Variant: /10docs sync

Skip pipeline. Push to Obsidian vault via bin/doc-sync.sh.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.