docs(builder-tools): add add_preset_approval, list_presets, flag_review_item#48
Open
docs(builder-tools): add add_preset_approval, list_presets, flag_review_item#48
Conversation
…ew_item Three builder tools shipped in recent SDK releases but were missing from the Builder Tools Reference: - add_preset_approval + list_presets (bitbadgesjs PR #179): preset approvals cut ~50% of output tokens by rendering canonical skill shapes from a params object. Output is structurally identical to raw add_approval, so presets are simply a cheaper path when the shape fits. - flag_review_item (bitbadgesjs PR #123 / BitBadgesBuilderAgent): agent self-surfaces assumptions, substitutions, and design choices during a build. Entries drain into BuildResult.reviewFlags and are always available. Agents reading this reference would previously not know these tools exist. The SDK skill instructions (skillInstructions.ts) already reference them in every skill that has a preset, so the doc page was the only surface that had drifted. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Fields shipped in SDK PRs #121, #122, #174, #176 but not in the BuildResult interface snippet on the Programmatic Agent page: - hardErrors (backwards-compat raw strings) - designDecisions (SDK PR #176 — ✓/✗/n-a informational checks about what the collection IS) - reviewFlags (agent-surfaced via flag_review_item — always populated) - durationMs (wall-clock duration) - inferredTokenType, inferredTokenTypeSource, inferredTokenTypeReasoning (SDK PR #174 smart token-type inference) Also cross-links to the Smart Token-Type Detection page for the three inference fields so readers don't have to dig through the class docs. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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
Three builder tools shipped in recent SDK releases but were missing from the Builder Tools Reference page. This drift meant agents reading the reference would not know they exist:
add_approval, so presets are simply a cheaper path when the shape fits.BuildResult.reviewFlags. Always available; no feature flag.The SDK skill instructions (
skillInstructions.ts) already referenceadd_preset_approval/list_presetsinside every skill that ships a preset, and the Programmatic Agent page already documentsreviewFlagson BuildResult — this page was the only surface that had drifted.Test plan
packages/bitbadgesjs-sdk/src/builder/tools/registry.ts(lines 166, 235, 237)skillInstructions.tsreferencesadd_preset_approvalin 13+ skill sectionsAuto-generated by the BitBadges DX audit agent (2026-04-24 run).
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com