Repository navigation
DOC-7267 Tell the command-api-mapping skill about the status file - #4481
Merged
Merged
Conversation
The sweep section said to leave generic-only and unsupported lists empty but not where to record why, so a future sweep would leave them showing the default message. It now points at data/command-api-mapping-status.json and the README section that defines its format. Directive: keep the reason in the status file, not in api_calls, other scripts read that shape Directive: sync and async statuses of one library can differ on purpose, check the filled data before calling a pair unpaired Ticket: DOC-7267 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
dwdougherty
approved these changes
Nov 5, 2026
Contributor
🧠 Redis MemoryFound 5 related items from repository history (5 new this commit):
Memory updated at 51b205c |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
command-api-mappingskill's sweep section now says to record generic-only and unsupported lists indata/command-api-mapping-status.json. Before this, a sweep following the skill would leave those lists empty and the tab would show the default message.Docs-only change to one skill file. The format itself is already in
build/command-api-mapping-README.md(merged in #4478); the skill points at it.Ticket: DOC-7267 (the follow-up work there uses this skill).
🤖 Generated with Claude Code
Note
Low Risk
Single markdown skill file with no runtime or data changes; only clarifies workflow for maintainers and agents.
Overview
Updates the command-api-mapping skill’s “Sweeping empty lists” section so sweeps document why a client stays empty, not only when to fill gaps.
For
generic_onlyandunsupported, the bullets now explicitly say to leave the per-command list empty and record the reason indata/command-api-mapping-status.json. A new paragraph spells out the JSON shape ({command: {client_id: "generic_only" | "unsupported"}}), that the API methods tab reads it only for empty lists, stale entries after fills, keeping status out ofapi_calls, and pointers tobuild/command-api-mapping-README.mdandgenericCallinconfig.toml.This is documentation-only in
.claude/skills/command-api-mapping/SKILL.md; the status file and tab behavior were already in place (e.g. #4478).Reviewed by Cursor Bugbot for commit 51b205c. Bugbot is set up for automated code reviews on this repo. Configure here.