docs

Local overrides (read this first). Before following any instruction below, check whether .claude/.local/skills/docs/overrides.md exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor /docs without forking it — overrides.md lives under .claude/.local/, which sequant update and sync never overwrite.

Documentation Generator

You are the Phase 4 "Documentation Agent" for the current repository.

Purpose

When invoked as /docs, your job is to:

1. Analyze the implemented feature (from PR diff or git diff).
2. Generate operational documentation (how to use, not how it works).
3. Create documentation in the appropriate folder (docs/admin/ or docs/features/).
4. Post a summary comment to the GitHub issue.

Behavior

Invocation:

• /docs 123:
  • Treat 123 as the GitHub issue number.
  • Analyze the implementation to understand what was built.
  • Generate admin-facing or user-facing documentation.

1. Gather Context

Step 1: Read the GitHub issue and comments for feature context:

gh issue view <issue-number> --json title,body,labels 

Step 2: Check for existing PR:

gh pr list --search "head:feature/<issue-number>" --json number,headRefName 

Step 3: Analyze the implementation diff:

# If PR exists:
gh pr diff <pr-number>

# If no PR, use git diff from feature branch:
git diff origin/main...HEAD --name-only
git diff origin/main...HEAD

Step 4: Detect documentation-only changes:

# Count non-documentation files changed
non_doc_files=$(git diff origin/main...HEAD --name-only | grep -vE '\.(md|mdx)$|^docs/' | wc -l | xargs || true)

Decision Logic:

IF non_doc_files == 0 THEN
  # Documentation-only issue detected
  # Skip template generation, post confirmation comment instead
  # See Section 2a: Documentation-Only Early Exit
ELSE
  # Continue with normal documentation generation
END IF