growilabs

Investigate a GitHub issue - fetch info, update labels, analyze code/reproduce, report findings, and optionally fix. Usage: /investigate-issue <issue-url-or-number>

GROWI main application (apps/app) specific commands and scripts. Auto-invoked when working in apps/app.

Auto-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`).

Organize and clean up specification documents after implementation completion. Removes implementation details while preserving essential context for future refactoring.

Initialize a new specification with detailed project description

Quick spec generation with interactive or automatic mode

GROWI apps/app Turbopack configuration, module optimization, and build measurement tooling. Auto-invoked when working in apps/app.

Fix broken symlinks in .next/node_modules/ — diagnose, decide allowlist vs dependencies, and verify

Set 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.

Save 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.

Draft 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.