Documentation Pipeline
Developer Official v1.2.0Analyzes source code and generates comprehensive technical documentation with examples, formatted as clean markdown
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 8 nodes
Documentation Pipeline
Analyzes source code and generates detailed technical documentation with examples, formatted as clean markdown
Documentation Writing
Produces technical documentation from code analysis, covering API references, guides, and module overviews
Example Generation
Produces practical, runnable usage examples in graded tiers from a code analysis, ready to merge into the documentation
Analyze Code
Extracts structural information from source code for documentation generation
Generate Examples
Creates practical, runnable usage examples showing common patterns and workflows
Write Documentation
Generates detailed technical documentation from code analysis output
Documentation Standards
Reference standards for technical documentation format, structure, and content quality
Documentation Checklist
Working checklist to track documentation completeness before publication
Requirements 1 service, 2 data types
- LLM Service
- source code
- pii
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling:
Version history 19 releases
GH#863 (K-045 intent/output-mismatch) — wire the `generate-examples` feeder into the execution DAG. It was defined but never invoked, so the code examples never reached the deliverable. Added a backing `example-generation` skill (from_step resolves by skill title), inserted the step between code analysis and documentation writing, and bound `write-documentation` to consume its output via explicit `from_step` bindings. Converted positional/title step refs in both prompts to `context_params` + `{{step.context.*}}`. Bound `language-polish` `source` to the Documentation Writing deliverable and re-pinned `polish-language` to 1.0.6.
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (code_analysis/text, documentation/text, formatted_docs/text, sanitised_docs/text, polished_docs/text, compliance_verdict/decision, consistency_verdict/decision). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.
GH#645 Row 3b — migrate to K-037 dep-referenced schema. Strip 10 inline shared-content files and declare 10 hub-shared deps (UUID id + slug name + version + checksum from `gen-dep-checksums.mjs`). Closes pre-Step-3 inline-vendoring for this bundle.
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Developer
View all →Bug Report Triage Pipeline
Classifies incoming bug reports, extracts structured details, and triages by severity using incident response guidelines
Big-Log Extractor & Summariser
Extracts the signal from a large log deterministically — pull matching lines, dedupe, count — then has a model summarise only the small, unique result, cutting tokens dramatically.
Webapp Testing Pipeline
Plan test cases, write and execute tests, report failures, and fix issues in an automated cycle