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.).
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
See AGENTS.md for the authoritative forbidden types list. If a fix requires a forbidden type, DO NOT FIX IT. Skip the error entirely.
| Error code | Description | Sub-skill |
|---|---|---|
[no-untyped-def] | Function missing type annotations | StreamFlow Mypy no-untyped-def Fixer skill |
[var-annotated] | Variable missing type annotation | StreamFlow Mypy var-annotated Fixer skill |
git diff | grep -E "Any\b|MutableMapping\[.*Any|MutableSequence\[.*Any|list\[Any|dict\[.*Any"
uv run make format-check codespell-check typing
None, bool, int, str, float, bytesWorkflow, Connector, Port, Token, etc.str | None, int | boollist[str], dict[str, int], set[Token]Self, type[MyClass], Literal["a", "b"]Prefer Literal over str/int for fixed value sets (statuses, connector types, mode flags).
Broad arguments, narrow returns: parameters use abstract types (Iterable, Sequence, Mapping); return types use concrete types (list, dict, set).
# Always annotate with concrete types
def process(self, workflow: Workflow, config: WorkflowConfig) -> bool: ...
# Self for classmethods
@classmethod
async def load(cls, persistent_id: int) -> Self: ...
# Optional: use X | None, not Optional[X]
def get(self, name: str) -> Connector | None: ...
# Always annotate return types — mypy strict mode requires it
async def close(self) -> None: ...
When in doubt, skip it. Better to leave an error than violate the forbidden types constraint.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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`.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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/`.
The English summary is being prepared. Showing the original 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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.