docs(base): clarify unsupported capability boundaries - #2133
Conversation
Consolidate the retained Base guidance into generic capability rules. Document unsupported view appearance settings, the current single-table copy contract, and unsupported field handling without carrying over same-name rename behavior or evaluation-specific command traces.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe Base documentation now defines unsupported view settings and field types. A contract test loads the documentation and verifies the required refusal guidance, including single-table copying and raw API boundaries. ChangesBase capability guidance
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Avoid an incomplete closed list of supported view properties and scope table-copy guidance to the user's requested resources. Replace evaluation-trace blacklists with three focused capability contract checks.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@shortcuts/base/base_capability_contract_test.go`:
- Around line 26-34: Extend the contract assertions in the test around the
existing view-appearance, single-table-copy, and unsupported-field-type checks
to require the mandated stop/refusal behaviors: “说明能力边界并停止”, “说明当前 CLI 不支持并停止”,
and the raw-API prohibition. Keep the existing trigger and guidance assertions,
and fail with targeted messages when any required action is missing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: f70c5174-581c-426a-a059-bfe949fe5fff
📒 Files selected for processing (3)
shortcuts/base/base_capability_contract_test.goskills/lark-base/SKILL.mdskills/lark-base/references/lark-base-field-json.md
1. Delete the prose-fragment assertions for the shipped Base skill guidance
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@ef548ee451812ae0de3417054a3159842ef9f269🧩 Skill updatenpx skills add huarenmin13/cli#agent/base-capability-boundaries -y -g |
Summary
Clarify Base agent behavior when a requested operation is outside the current CLI/OpenAPI capability surface. This consolidates two evaluated guidance changes into one minimal patch, while avoiding the general create-semantics guidance already covered by #2114.
The root failure mode was repeated exploration of unsupported view properties or field types, plus ambiguity around the scope and verification of single-table copies. This change turns those cases into explicit, reusable boundaries without changing API request behavior.
Changes
+table-copyshortcut: compose existing commands according to the user-requestedschema,records, andviewsscope, and use the existing write-response-first verification rule.Scope intentionally excludes the same-name view auto-rename implementation and does not repeat #2114 generic create-evidence rule.
Test Plan
go test -count=1 ./shortcuts/basemake unit-testgo vet ./...gofmt -l .produces no outputgo mod tidyleavesgo.modandgo.sumunchangedgo run github.com/golangci/golangci-lint/v2/cmd/golangci-lint@v2.1.6 run --new-from-rev=upstream/mainreports 0 issuesmake buildand current-branch embedded Skill read expose all three boundariesRelated Issues
Summary by CodeRabbit
Documentation
Tests