使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/poteto/noodle --skill commit开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Conventional Commits
Follow these project-specific rules when creating commits.
Branching
Never create bare branches. If you need branch isolation, use the worktree skill. For simple changes, commit directly on the current branch (including main). Do not run git checkout -b.
Project Rules
- One commit per logical change — never combine unrelated fixes or features. Three independent changes = three commits.
- Only commit files you changed — never pull in unrelated files from concurrent sessions.
- Always include a body — no title-only commits. Explain what and why.
- `merge` type — use
merge(not a merge commit) when merging a worktree or feature branch. - Sequence commits to maximise option value — foundational infrastructure first, then features that build on it.
Example
feat(alerts): Add Slack thread replies for alert updates
When an alert is updated or resolved, post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped together.