菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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/`.
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.
This skill should be used when the user asks to "write a test", "run tests", "add a test for", "test this function", "check test coverage", "run the test suite", or when writing pytest tests for StreamFlow features or bug fixes.
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.
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`.
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.
| name | StreamFlow Git Workflow |
| description | 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. |
| version | 0.1.0 |
Commit message conventions and CHANGELOG update rules for StreamFlow. The approval rule (never commit without explicit user approval) lives in AGENTS.md.
<Type> <subject>
<body>
| Type | When to use |
|---|---|
Add | Wholly new feature or file |
Fix | Bug fix |
Refactor | Code change with no behavior change |
Update | Enhancement to an existing feature |
Remove | Deletion of code or files |
Bump | Dependency version update |
Implement | New implementation of an existing interface |
Improve | Performance or quality improvement |
Docs | Documentation only |
Test | Test additions or changes |
Subject line:
Add restore method to DataManagerBody (required except for trivial changes like typo fixes):
Fixes #123, Closes #456Before every commit, CHANGELOG.md must be updated under ## [Unreleased]. Load the StreamFlow Changelog Update skill for the full rules on which subsection to use, entry format, and what to avoid.
Add restore method to DataManager
Implement restore method to enable workflow recovery from checkpoints.
This allows jobs to resume from the last completed step.
Fix SSH connector authentication timeout (Fixes #931)
Increase default timeout for SSH authentication from 5s to 30s to handle
slow networks and high-latency connections.
Bump kubernetes-asyncio from 33.3.0 to 34.3.3
Refactor DirectedGraph class
Extract graph traversal logic into dedicated methods to reduce coupling
and improve testability of scheduling algorithms.