code-style-guide
Project coding standards and style guidelines. Always follow these conventions when writing or reviewing code.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 1.4k
- Forks
- 767
01 前言 Front Matter
- name
- code-style-guide
- license
- MIT
- description
- Project coding standards and style guidelines. Always follow these conventions when writing or reviewing code.
03 SKILL.md 正文
Code Style Guide
Follow these conventions for all code in this project.
Python
- Use 4 spaces for indentation
- Maximum line length: 88 characters (Black default)
- Use type hints for function signatures
- Prefer f-strings over
.format()or%formatting
Naming Conventions
- Classes:
PascalCase - Functions/variables:
snake_case - Constants:
UPPER_SNAKE_CASE - Private members:
_leading_underscore
Documentation
- All public functions must have docstrings
- Use Google-style docstrings
- Include type information in docstrings when not using type hints
04 同仓库更多 Skills
verify-sdk
This skill should be used to "verify SDK behavior", "check an SDK change against the feature map", "run the SDK feature map", "maintain the SDK feature map", or "run the daily SDK map pass". It holds the maintained map of what the OpenHands SDK does in-process (agent loop, LLMs, conversations, events, condensers, skills, plugins, MCP, hooks, sub-agents, critic, security, tools, workspaces, settings, observability, ACP), the control-sdk driver its recipes use, and sdk-map (check, owners, baseline, run, report).
only
The one component in a fixed location this format discovers.
never
Must never be discovered; the manifest is rejected first.
good
Loads while its broken sibling is skipped.
broken
暂无简介
ok
Loads despite the two non-fatal manifest violations.