growilabs
- 36 skills
- 0 followers
- 7 hours ago last updated
- ▌ Kiro Impl · growilabs bundleImplement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
- ▌ Kiro Steering · growilabs bundleMaintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
- ▌ Kiro Discovery · growilabsEntry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.
- ▌ Kiro Spec Batch · growilabsCreate complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.
- ▌ Kiro Spec Tasks · growilabs bundleGenerate implementation tasks from requirements and design. Use when creating actionable task lists.
- ▌ Kiro Spec Design · growilabs bundleGenerate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.
- ▌
- ▌ Kiro Validate Gap · growilabs bundleAnalyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.
- ▌ Kiro Steering Custom · growilabs bundleCreate custom steering documents for specialized project contexts. Use when creating domain-specific steering files.
- ▌ Kiro Validate Design · growilabs bundleInteractive technical design quality review and validation. Use when reviewing design before implementation.
- ▌ Kiro Spec Requirements · growilabs bundleGenerate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
- ▌ Growi Upgrade Guide · growilabs bundleDraft GROWI upgrade guide pages (docs/{ja,en}/admin-guide/upgrading/NNx.md) from GitHub release notes, register them in the VuePress sidebar, and apply GROWI-specific conventions (bilingual ja/en pair, section tag prefixes like [新機能]/[改善], and ContextualBlock splits between docs-growi-org and help-growi-cloud). Use this skill whenever the user asks to create or update an upgrade guide, aftermath notes, or "upgrading to vX" documentation for a new GROWI minor/major release — even if they only say "write up v7.6" or similar shorthand.
- ▌ Kiro Review · growilabsReview a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
- ▌
- ▌ Detect Flaky CI · growilabsScan recent GROWI CI runs for flaky (non-deterministic) job/test failures and track them as GitHub issues. Detection only — never modifies source code. Usage - /detect-flaky-ci [--window-hours=N] [--vitest-threshold=N]
- ▌
- ▌
- ▌ Kiro Spec Cleanup · growilabsOrganize and clean up specification documents after implementation completion. Removes implementation details while preserving essential context for future refactoring.
- ▌ Kiro Validate Impl · growilabsValidate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
- ▌ Mongoose To Prisma · growilabsMigrate a single Mongoose model file to Prisma, following GROWI's established patterns. Step-by-step with human approval at each stage.
- ▌ Essential Test Design · growilabsWrite tests that verify observable behavior (contract), not implementation details. Auto-invoked when writing or reviewing tests.
- ▌ App Commands · growilabsGROWI main application (apps/app) specific commands and scripts. Auto-invoked when working in apps/app.
- ▌ Investigate Flaky Test · growilabsInvestigate a GROWI flaky-test tracking issue (created by detect-flaky-ci) - reproduce, find the root cause, decide test-fix vs product-fix vs quarantine, and optionally open a PR. Usage - /investigate-flaky-test <issue-url-or-number> [--auto]
- ▌ Suggest Path Evaluator · growilabs bundleEvaluate the quality of GROWI's suggest-path output by judging each proposed save-path as o (usable) / △ (usable but improvable) / x (not usable) for a document, with a wiki-agnostic plausibility rubric — NOT by matching one "correct" path. For each document it reads the wiki content (page bodies, not just path strings), judges each candidate against THIS wiki's own organization, AND drills down the tree to build the document's own ideal home so a candidate is only ruled x once a better place is known (multiple candidates may be usable — the correct place is not unique). Use it to score suggest-path's proposals as a reviewer would — e.g. "evaluate suggest-path on this document", "score / check / review these path suggestions", "are these save paths usable", "how good is suggest-path for this wiki", or when dogfooding suggest-path and you want a per-candidate verdict instead of eyeballing it. Trigger it even when the user only says "check"/"score"/"review" suggest-path results without the word "evaluator".
- ▌ Essential Test Patterns · growilabsGROWI testing patterns with Vitest, React Testing Library, and vitest-mock-extended (type-safe mocking, avoid type assertions). Auto-invoked when writing or reviewing tests.
- ▌ App Architecture · growilabsGROWI main application (apps/app) architecture, directory structure, and design patterns. Auto-invoked when working in apps/app.
- ▌ Build Optimization · growilabsGROWI apps/app Turbopack configuration, module optimization, and build measurement tooling. Auto-invoked when working in apps/app.
- ▌ Esm Merge Coverage · growilabs bundleESM-ify source files that arrive from a pre-ESM branch when merging into apps/app. Use after merging any branch that predates the v8 ESM migration (long-lived feature branches cut from v7-era master, v7.5 maintenance work) into master or a v8 branch — a git merge does NOT re-run any ESM transform, so incoming CJS/extension-bearing sources slip in silently and only break at build/runtime. Auto-invoked when the conversation is about merging a pre-ESM branch into apps/app and bringing the result up to the ESM convention.
- ▌ App Specific Patterns · growilabsGROWI main application (apps/app) specific patterns for Next.js, Jotai, SWR, and testing. Auto-invoked when working in apps/app.
- ▌ Vendor Styles Components · growilabsVendor CSS precompilation system for Turbopack compatibility. How to add third-party CSS to components without violating Pages Router global CSS restriction. Auto-invoked when working in apps/app.
- ▌ Next Express Route Consistency · growilabsCross-check the Express-exclusive path list in src/utils/is-next-page-route.ts against the real route registrations in server/routes/index.js and the page files under src/pages/**. Auto-invoked when editing server/routes/index.js, src/utils/is-next-page-route.ts, or src/components/ReactMarkdownComponents/NextLink.tsx, or when asked to check whether NextLink's routing predicate is stale.
- ▌ Fix Broken Next Symlinks · growilabsFix broken symlinks in .next/node_modules/ — diagnose, decide allowlist vs dependencies, and verify
- ▌ Page Save Origin Semantics · growilabsAuto-invoked when modifying origin-based conflict detection, revision validation logic, or isUpdatable() method. Explains the two-stage origin check mechanism for conflict detection and its separation from diff detection.
- ▌ Page Transition And Rendering Flow · growilabsAuto-invoked when modifying page transition logic, global atom hydration, or the `[[...path]]` dynamic route. Explains the data flow from SSR/client navigation to page rendering, and the hydration-vs-subsequent-sync rule for global atoms (`currentPathnameAtom`, `currentUserAtom`, `isMaintenanceModeAtom`).
- ▌ Growi MCP Setup · growilabsSet up and connect the GROWI MCP server so GROWI tools become available to the agent. Use this skill when the user asks to "set up GROWI", "connect GROWI", "configure the GROWI MCP server", or when GROWI tools (such as suggestPath, searchPages, createPage) are expected but not available. Also use this right after the user has installed the GROWI plugin/skill and needs to finish wiring up the connection.
- ▌ Growi Smart Save · growilabs bundleSave content to GROWI wiki with intelligent path suggestions. Use this skill when the user asks to save, store, or archive content to GROWI. Triggers on: "save to GROWI", "store this in the wiki", "save this page", or any request to persist content in GROWI. Also use when the user uploads a document and wants it stored in GROWI, or after a conversation session the user wants to capture as a wiki page. Also use when the user asks for a slower, higher-accuracy destination search ("use the Vault", "take your time and find the right place").