autojanet/skills/documentation-generation-doc-generate/SKILL.md
Zoë cc74ad0bd0
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
fix: use library/ Harbor project, add skills, fix pipeline secrets
- .woodpecker.yaml: image paths -> library/autojanet-{agent,dispatcher}
- .woodpecker.yaml: secret names RS_HARBOR_USER / RS_HARBOR_PASS (global)
- container/Dockerfile: restore COPY skills/, skills/ populated from opencode config
- skills/: 84 opencode skills bundled into image
- k8s/manifests: update image refs to library/
2026-05-30 15:43:14 -07:00

1.8 KiB

name description risk source date_added
documentation-generation-doc-generate You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI... unknown community 2026-02-27

Automated Documentation Generation

You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.

Use this skill when

  • Generating API, architecture, or user documentation from code
  • Building documentation pipelines or automation
  • Standardizing docs across a repository

Do not use this skill when

  • The project has no codebase or source of truth
  • You only need ad-hoc explanations
  • You cannot access code or requirements

Context

The user needs automated documentation generation that extracts information from code, creates clear explanations, and maintains consistency across documentation types. Focus on creating living documentation that stays synchronized with code.

Requirements

$ARGUMENTS

Instructions

  • Identify required doc types and target audiences.
  • Extract information from code, configs, and comments.
  • Generate docs with consistent terminology and structure.
  • Add automation (linting, CI) and validate accuracy.
  • If detailed examples are required, open resources/implementation-playbook.md.

Safety

  • Avoid exposing secrets, internal URLs, or sensitive data in docs.

Output Format

  • Documentation plan and artifacts to generate
  • File paths and tooling configuration
  • Assumptions, gaps, and follow-up tasks

Resources

  • resources/implementation-playbook.md for detailed examples and templates.