本文へ移動
cccskills
無料GitHub で公開

StreamFlow Documentation

This skill should be used when the user asks to "write documentation", "add a doc page", "update RST files", "add a tutorial", or when writing or editing Sphinx RST documentation for StreamFlow.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.9 KB
  • examples/SKILL.md2.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

StreamFlow Documentation Skill

Guidelines for writing Sphinx RST documentation for StreamFlow. Docs live under docs/source/. The Sphinx build uses sphinx.ext.autosectionlabel, so every section title is automatically a valid :ref: target.

Writing Style

  • Use American English throughout.
  • Use double backticks for all code entities: file names, environment variables, class names, function names, CLI commands, YAML keys, CWL fields.
  • Never reference a file without first telling the user how to create it.
  • Keep source files shown via literalinclude within 80 characters per line.

RST Conventions

All documentation files use .rst format.

Section title underlines

Every title underline (and overline) must be exactly as long as the title text — no shorter, no longer. Count Unicode characters, not bytes.

MPI Application
===============    ← 15 chars, underline is 15 chars  ✓

Run with Kubernetes
-------------------  ← 19 chars, underline is 19 chars  ✓

After editing headings, verify with:

python3 -c "
with open('docs/source/.../file.rst') as f:
    lines = f.readlines()
ul = set('=-~^\"\\'\`#*+')
for i,l in enumerate(lines):
    s = l.rstrip()
    if i+1 < len(lines):
        n = lines[i+1].rstrip()
        if n and len(set(n))==1 and n[0] in ul and len(s)!=len(n):
            print(f'Line {i+1}: title={len(s)}, underline={len(n)}: {s!r}')
"

Highlighting changed lines

Use :emphasize-lines: with both code-block and literalinclude directives. Prefer literalinclude whenever the file exists on disk.

When a tutorial shows multiple versions of the same file for different environments (e.g. Docker Compose → Kubernetes → Helm variants of streamflow.yml), use :emphasize-lines: to highlight the lines that differ from the base version, so the reader can spot the changes at a glance:

.. literalinclude:: streamflow-k8s.yml
   :language: yaml
   :emphasize-lines: 12, 16, 20-25

Cross-references

Use :ref: to link to other sections. Targets are section titles verbatim:

:ref:`DockerComposeConnector`
:ref:`Put it all together`

Common targets: Install, Write your workflow, Put it all together, Binding steps and deployments, Import your environment, CWL Runner, DockerComposeConnector, KubernetesConnector, Helm4Connector.

Subskills

TaskSubskill
Add a new worked example tutorialStreamFlow Documentation — Adding Examples

See Also

  • StreamFlow Code Style skill — Python code style and docstring conventions
  • StreamFlow Git Workflow skill — commit message format

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

This skill should be used when the user asks to "update the changelog", "add a changelog entry", "write a CHANGELOG entry", or when preparing a git commit in StreamFlow that requires updating the `## [Unreleased]` section of `CHANGELOG.md`.

日本語の概要は準備中です。原文の説明を表示しています。

alpha-unito/streamflow662026年10月9日 更新

This skill should be used when the user asks to "add docstrings", "write error handling", "use naming conventions", "handle exceptions", or when writing new Python code for StreamFlow that requires docstring format, naming conventions, exception handling, or async cleanup patterns.

日本語の概要は準備中です。原文の説明を表示しています。

alpha-unito/streamflow662026年10月9日 更新

This skill should be used when the user asks to "add an example", "write a tutorial", "document a new workflow example", or when creating a new worked example under `docs/source/examples/`.

日本語の概要は準備中です。原文の説明を表示しています。

alpha-unito/streamflow662026年10月9日 更新

This skill should be used when the user asks to "write a commit message", "create a commit", "format a commit", "what commit type to use", or when preparing changes for a git commit in StreamFlow. Provides commit message format, type conventions, and examples.

日本語の概要は準備中です。原文の説明を表示しています。

alpha-unito/streamflow662026年10月9日 更新

This skill should be used when the user encounters "no-untyped-def" mypy errors, asks to "fix no-untyped-def errors", "add type annotations to functions", or mentions "Function is missing a type annotation". Provides specific workflow for fixing missing type annotations while respecting forbidden type constraints.

日本語の概要は準備中です。原文の説明を表示しています。

alpha-unito/streamflow662026年10月9日 更新

This skill should be used when the user asks to "fix mypy errors", "add type annotations", "fix type checking", "resolve no-untyped-def", "fix mypy type errors", or when working with type hints while respecting StreamFlow's forbidden type constraints (no Any, dict[str, Any], etc.).

日本語の概要は準備中です。原文の説明を表示しています。

alpha-unito/streamflow662026年10月9日 更新

alpha-unito のスキルをすべて見る

このスキルの問題を報告する