We want to ration our client agent's context window. When the page subcommand is used, it loads the full text. Instead, it should only load the high-level table of contents so that future commands can grab the exact needed section. There still needs to be a way to access the entire page. Consider a good UX, perhaps --complete or --section All?
Decide on what an agent would be most comfortable with, then implement.
Remember to update the SKILL.md and unit tests as necessary.
We want to ration our client agent's context window. When the `page` subcommand is used, it loads the full text. Instead, it should only load the high-level table of contents so that future commands can grab the exact needed section. There still needs to be a way to access the entire page. Consider a good UX, perhaps `--complete` or `--section All`?
Decide on what an agent would be most comfortable with, then implement.
Remember to update the SKILL.md and unit tests as necessary.
**Claude finished @sam's task** —— [View job](http://100.100.131.50:3000/sam/claude-plugin-runescape/actions/runs/13)
---
### Implementation Plan
- [x] Gather context and understand request
- [x] Read CLAUDE.md and explore codebase
- [x] Check for existing claude branch (none found, created `claude/issue-3-page-default-summary`)
- [x] Understand current `page` command implementation
- [x] Implement changes: default to TOC/summary, add `--complete` flag
- [x] Update SKILL.md
- [x] Commit and push changes
- [x] Create PR
### Summary
Implemented the change in `scripts/rsw/internal/cmd/page.go`:
- **Default behavior** (`rsw <game> page <title>`): now shows only the table of contents (section list) plus a hint message — no full page content dumped
- **`--complete` flag**: fetches the full page content (restores old default behavior)
- **`--section <name>`**: unchanged
The `SKILL.md` was updated with the new recommended 2-step workflow: call `page` (TOC) first, then `page --section <name>` for the content needed.
Note: No existing unit tests covered the cmd layer behavior — only integration tests for the wiki client exist, which are unchanged.
**PR:** https://git.samlab.cloud/sam/claude-plugin-runescape/pulls/4
**Branch:** `claude/issue-3-page-default-summary`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We want to ration our client agent's context window. When the
pagesubcommand is used, it loads the full text. Instead, it should only load the high-level table of contents so that future commands can grab the exact needed section. There still needs to be a way to access the entire page. Consider a good UX, perhaps--completeor--section All?Decide on what an agent would be most comfortable with, then implement.
Remember to update the SKILL.md and unit tests as necessary.
@claude please implemet
Claude finished @sam's task —— View job
Implementation Plan
claude/issue-3-page-default-summary)pagecommand implementation--completeflagSummary
Implemented the change in
scripts/rsw/internal/cmd/page.go:rsw <game> page <title>): now shows only the table of contents (section list) plus a hint message — no full page content dumped--completeflag: fetches the full page content (restores old default behavior)--section <name>: unchangedThe
SKILL.mdwas updated with the new recommended 2-step workflow: callpage(TOC) first, thenpage --section <name>for the content needed.Note: No existing unit tests covered the cmd layer behavior — only integration tests for the wiki client exist, which are unchanged.
PR: #4
Branch:
claude/issue-3-page-default-summary