all publishers

growilabs

@growilabs source repo

47 published skills

  1. ▌
    Kiro Impl 2 · growilabs bundle
    Implement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
    1.5k repo stars
  2. ▌
    Kiro Steering 2 · growilabs bundle
    Maintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
    1.5k repo stars
  3. ▌
    Kiro Discovery 2 · growilabs
    Entry 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.
    1.5k repo stars
  4. ▌
    Kiro Spec Batch 2 · growilabs
    Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.
    1.5k repo stars
  5. ▌
    Kiro Spec Tasks 2 · growilabs bundle
    Generate implementation tasks from requirements and design. Use when creating actionable task lists.
    1.5k repo stars
  6. ▌
    Kiro Spec Design 2 · growilabs bundle
    Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.
    1.5k repo stars
  7. ▌
    Kiro Spec Status 2 · growilabs
    Show specification status and progress
    1.5k repo stars
  8. ▌
    Kiro Validate Gap 2 · growilabs bundle
    Analyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.
    1.5k repo stars
  9. ▌
    Kiro Steering Custom 2 · growilabs bundle
    Create custom steering documents for specialized project contexts. Use when creating domain-specific steering files.
    1.5k repo stars
  10. ▌
    Kiro Validate Design 2 · growilabs bundle
    Interactive technical design quality review and validation. Use when reviewing design before implementation.
    1.5k repo stars
  11. ▌
    Kiro Spec Requirements 2 · growilabs bundle
    Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
    1.5k repo stars
  12. ▌
    Kiro Impl · growilabs bundle
    Implement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
    1.5k repo stars
  13. ▌
    Kiro Steering · growilabs bundle
    Maintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
    1.5k repo stars
  14. ▌
    Kiro Discovery · growilabs
    Entry 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.
    1.5k repo stars
  15. ▌
    Kiro Spec Batch · growilabs
    Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.
    1.5k repo stars
  16. ▌
    Kiro Spec Tasks · growilabs bundle
    Generate implementation tasks from requirements and design. Use when creating actionable task lists.
    1.5k repo stars
  17. ▌
    Kiro Spec Design · growilabs bundle
    Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.
    1.5k repo stars
  18. ▌
    Kiro Spec Status · growilabs
    Show specification status and progress
    1.5k repo stars
  19. ▌
    Kiro Validate Gap · growilabs bundle
    Analyze implementation gap between requirements and existing codebase. Use when planning integration with existing systems.
    1.5k repo stars
  20. ▌
    Kiro Steering Custom · growilabs bundle
    Create custom steering documents for specialized project contexts. Use when creating domain-specific steering files.
    1.5k repo stars
  21. ▌
    Kiro Validate Design · growilabs bundle
    Interactive technical design quality review and validation. Use when reviewing design before implementation.
    1.5k repo stars
  22. ▌
    Kiro Spec Requirements · growilabs bundle
    Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
    1.5k repo stars
  23. ▌
    Growi Upgrade Guide · growilabs bundle
    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.
    1.5k repo stars
  24. ▌
    Kiro Review · growilabs
    Review 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.
    1.5k repo stars
  25. ▌
    Kiro Spec Init · growilabs
    Initialize a new specification with detailed project description
    1.5k repo stars
  26. ▌
    Detect Flaky CI · growilabs
    Scan 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]
    1.5k repo stars
  27. ▌
    Kiro Spec Quick · growilabs
    Quick spec generation with interactive or automatic mode
    1.5k repo stars
  28. ▌
    Investigate Issue · growilabs
    investigate-issue
    1.5k repo stars
  29. ▌
    Kiro Spec Cleanup · growilabs
    Organize and clean up specification documents after implementation completion. Removes implementation details while preserving essential context for future refactoring.
    1.5k repo stars
  30. ▌
    Kiro Validate Impl · growilabs
    Validate feature-level integration after all tasks are implemented. Checks cross-task consistency, full test suite, and overall spec coverage.
    1.5k repo stars
  31. ▌
    Mongoose To Prisma · growilabs
    Migrate a single Mongoose model file to Prisma, following GROWI's established patterns. Step-by-step with human approval at each stage.
    1.5k repo stars
  32. ▌
    Essential Test Design · growilabs
    Write tests that verify observable behavior (contract), not implementation details. Auto-invoked when writing or reviewing tests.
    1.5k repo stars
  33. ▌
    App Commands · growilabs
    GROWI main application (apps/app) specific commands and scripts. Auto-invoked when working in apps/app.
    1.5k repo stars
  34. ▌
    Investigate Flaky Test · growilabs
    Investigate 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]
    1.5k repo stars
  35. ▌
    Suggest Path Evaluator · growilabs bundle
    Evaluate 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".
    1.5k repo stars
  36. ▌
    Essential Test Patterns · growilabs
    GROWI testing patterns with Vitest, React Testing Library, and vitest-mock-extended (type-safe mocking, avoid type assertions). Auto-invoked when writing or reviewing tests.
    1.5k repo stars
  37. ▌
    App Architecture · growilabs
    GROWI main application (apps/app) architecture, directory structure, and design patterns. Auto-invoked when working in apps/app.
    1.5k repo stars
  38. ▌
    Build Optimization · growilabs
    GROWI apps/app Turbopack configuration, module optimization, and build measurement tooling. Auto-invoked when working in apps/app.
    1.5k repo stars
  39. ▌
    Esm Merge Coverage · growilabs bundle
    ESM-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.
    1.5k repo stars
  40. ▌
    App Specific Patterns · growilabs
    GROWI main application (apps/app) specific patterns for Next.js, Jotai, SWR, and testing. Auto-invoked when working in apps/app.
    1.5k repo stars
  41. ▌
    Vendor Styles Components · growilabs
    Vendor 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.
    1.5k repo stars
  42. ▌
    Next Express Route Consistency · growilabs
    Cross-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.
    1.5k repo stars
  43. ▌
    Fix Broken Next Symlinks · growilabs
    Fix broken symlinks in .next/node_modules/ — diagnose, decide allowlist vs dependencies, and verify
    1.5k repo stars
  44. ▌
    Page Save Origin Semantics · growilabs
    Auto-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.
    1.5k repo stars
  45. ▌
    Page Transition And Rendering Flow · growilabs
    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`).
    1.5k repo stars
  46. ▌
    Growi MCP Setup · growilabs
    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.
    1.5k repo stars
  47. ▌
    Growi Smart Save · growilabs bundle
    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. Also use when the user asks for a slower, higher-accuracy destination search ("use the Vault", "take your time and find the right place").
    1.5k repo stars