docs: improve agent contribution guidance - #2259
Conversation
|
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 (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAGENTS.md was rewritten with rules for implementation discipline, build prerequisites, surface selection, hard contracts, structured errors, affordances, skills, testing, validation, CI checks, maintenance, and contribution requirements. ChangesRepository 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 |
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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 `@AGENTS.md`:
- Around line 46-60: Update the Build section in AGENTS.md to state that `go
build .` uses the tracked `internal/registry/meta_data_default.json` stub when
`scripts/fetch_meta.py` is not run, while the fetch script provides the full
metadata catalog. Remove the reference to `internal/registry/meta_data.json`
from the later prerequisite guidance, without changing the build commands or
product code.
- Around line 79-111: Fix the JSON output contract reference in the Hard
Contracts section of AGENTS.md by pointing it to an existing README section
anchor, or add the missing JSON output contract anchor to README.md before
retaining the link. Ensure the link resolves to the actual contract
documentation.
- Around line 129-145: Add a reachable-content test that reads shipped
documentation through the embedded content path, registering embeddedContentFS
via cmd.SetEmbeddedSkillContent and/or cmd.SetEmbeddedAffordanceContent, or
exercising the real skills read/docs flow in tests/plugin_e2e/skills_test.go.
Ensure the test fails when content_embed.go lists a path that is missing or
unreadable from the embedded filesystem, while preserving the existing
missing/partial embed coverage.
- Around line 195-205: Update the Go PR validation instructions near the pinned
go run checks to state that Go must be able to download uncached modules through
the configured module proxy, or document an equivalent offline/cache setup
before running them. Keep the existing pinned commands unchanged.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@b76845a85b348593a605c090931dd9e633e74167🧩 Skill updatenpx skills add larksuite/cli#docs/optimize-agents-md -y -g |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2259 +/- ##
=======================================
Coverage 76.36% 76.36%
=======================================
Files 1011 1011
Lines 111269 111269
=======================================
Hits 84970 84970
Misses 19815 19815
Partials 6484 6484 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
Rework the root
AGENTS.mdinto concise, project-specific guidance that helps coding agents choose the correct implementation owner, preserve CLI contracts, and validate changes without mistaking environment failures for product bugs.Changes
Test Plan
git diff --check origin/main...HEADlark-cli <domain> <command>verification — not applicable; runtime behavior is unchanged.Related Issues
Summary by CodeRabbit