chore(skill): sync workleap-squide skill with docs - #702
Open
claude[bot] wants to merge 1 commit into
Open
Conversation
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
Reviewed every in-scope page under
docs/againstagent-skills/workleap-squide/. The skill was already in sync on nearly everything; three items needed correcting.Fixed a wrong package in an import (
references/integrations.md)The "Apply a Backend Preferred Language Setting" example imported
useChangeLanguagefrom@squide/firefly. It is only exported from@squide/i18next(docs/reference/i18next/useChangeLanguage.md,packages/i18next/src/index.ts), and@squide/fireflydoes not re-export@squide/i18next, so the snippet would not have compiled. The skill's two otheruseChangeLanguagesnippets already imported it correctly. Note the same bad import exists upstream indocs/integrations/setup-i18next.md.Documented the navigation item
keyfallback (references/hooks-api.md)docs/reference/routing/useRenderedNavigationItems.mddocuments that when an item declares no$id, thekeyhanded torenderItemdefaults to a value computed fromindexandlevel, which cannot keep the menu from flickering across deferred registration updates. The skill described thekeyparameter's type but never said what it holds.Documented
$visibilityon a nested route (references/runtime-api.md)docs/reference/runtime/FireflyRuntime.mdanddocs/essentials/register-routes.mdboth cover declaring a nested route's visibility through the$visibilityoption, alongsideregisterPublicRoutefor a root public route. The skill listed$visibilityas a route property but had no example.Bumped
metadata.versionto1.27. Validation passed 21/21 on coverage with no remaining skill-vs-docs discrepancies.Not changed — upstream docs drift
references/patterns.mddocumentsReadonlySessionLocalStoragefrom@squide/fakes, faithfully mirroringdocs/reference/fakes/ReadonlySessionLocalStorage.md. That symbol no longer exists:packages/fakes/src/index.tsnow exportsLocalStorageSessionAccessor(same constructor option andgetSession()). Left the skill alone since the docs are its source of truth — the docs should be updated first, and the next sync will carry the change into the skill.🤖 Generated with Claude Code