check-an-api-pagination-loop
Check an API pagination loop for cursor handling, termination, duplicates, omissions, mutation, rate limits, retries, and bounded memory. Use when a client must traverse a changing collection safely.
来源信息
- 仓库
- protosphinx/sphinxstack
- 最近来源活动
- 2026年7月29日 13:55
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 3
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
文件资源管理器
2 个文件正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- check-an-api-pagination-loop
- category
- code
- description
- Check an API pagination loop for cursor handling, termination, duplicates, omissions, mutation, rate limits, retries, and bounded memory. Use when a client must traverse a changing collection safely.
# check-an-api-pagination-loop
## When to use
- Use with the exact API contract and representative fixture.
- Do not assume page size, order, or cursor stability.
## Procedure
1. Record contract, ordering, cursor opacity, snapshot semantics, limits, and error rules.
2. Preserve cursors without decoding or constructing them.
3. Test first, middle, last, empty, short, and repeated pages.
4. Detect cursor nonadvance, cycles, duplicate identity, omission, and changed ordering.
5. Handle retry, expiry, mutation, rate limit, cancellation, and resume.
6. Stream or checkpoint results within memory and side-effect bounds.
## Failure plan
- Stop on cursor cycles or ambiguous progress rather than looping or silently skipping.
## Worked example
A repeated next cursor is detected after three pages, preventing an infinite import.
## Done
- A pagination test report records contract, pages, cursors, identities, termination, mutation, retries, and resource use
- Empty, last, cycle, duplicate, omission, expiry, rate, cancellation, and resume tests verify traversal
在 GitHub 查看