chatto-pr-checklist
Check a Chatto pull request before review or merge. Use when opening a PR or when asked to check one.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-12
- Stars
- ★ 2.9k
- Forks
- 150
01 前言 Front Matter
- name
- chatto-pr-checklist
- description
- Check a Chatto pull request before review or merge. Use when opening a PR or when asked to check one.
03 SKILL.md 正文
Chatto PR Checklist
Review the complete branch diff against the target branch.
- Check tests for the changed behavior. Add missing coverage within the task.
- Check the documentation listed in root
AGENTS.md. Update affected records and public docs within the task. - Review Sweet notes using Writing change notes: describe the result for the reader and required upgrade actions, with one short entry per meaningful change rather than implementation instructions. An amendment may update an existing unreleased note in the same release unit, or combine notes and remove duplicates. Check that the combined note preserves required upgrade actions and the appropriate release type.
- For public API or protocol changes, use chatto-api-compatibility.
- For frontend changes, use chatto-frontend-review.
- Follow root
AGENTS.mdfor commit titles, PR status, and issue links.
For a review-only request, report findings without edits. Report only items that need action. This checklist does not authorize changes to agent instructions, branch names, or remote repositories.
PR Description
Explain the problem, resulting behavior, and important design decisions. List the checks run, their results, and any checks still needed. State relevant compatibility, migration, security, or deployment effects.
Use enough detail for the change. After creating or updating a PR, read its stored description and check that it matches the complete diff.
04 同仓库更多 Skills
writing-tests
Instructions and hints for writing tests.
update-project-dependencies
Update Chatto Go and frontend dependencies within their compatible version ranges, then run tests.
svelte-docs
Look up official Svelte, SvelteKit, and Svelte CLI documentation.
svelte-core-bestpractices
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.
svelte-code-writer
CLI tools for Svelte 5 documentation lookup and code analysis. MUST be used whenever creating, editing or analyzing any Svelte component (.svelte) or Svelte module (.svelte.ts/.svelte.js). If possible, this skill should be executed within the svelte-file-editor agent for optimal results.
session-wrap-up
Review a completed, paused, or blocked coding-agent session to identify friction, mistakes, near misses, missing context, and opportunities to improve future work. Use when the user asks to wrap up, run a retrospective, explain what issues the agent faced, capture lessons learned, or recommend improvements to repository instructions, documentation, skills, tooling, tests, or workflows. Produce an evidence-based, propose-only report; do not apply follow-up changes unless the user asks.