Agent Skills by crowi
Showing 20 vetted skills indexed across 1 GitHub repositories.
crowicrowi-role-manager
Restores the manager role session state, watchers, and inbox for Crowi orchestration.
crowicrowi-complete-feature
Validates worktree changes against objective gates and signals readiness for merge.
crowicrowi-deps
Resolves GitHub Dependabot security alerts by bumping dependencies and validating with pnpm.
crowicrowi-feature
Drives Crowi 2.0 feature development from approved spec through plan, implement, review, and commit phases.
crowicrowi-changesets
Decides when to add changesets and selects bump levels and target packages for Crowi releases.
crowicrowi-release-discord-nits
Generates categorized one-line Discord release comments from CHANGELOG diffs between git tags.
crowiintegrate-worktree
Merges finished git worktree branches into main, closes worktrees, and runs post-merge quality checks.
crowicrowi-docs-refresh
Updates Crowi site documentation against merged code changes and fixes stale claims.
crowicrowi-pr-received
Triages external GitHub pull requests via remote diffs with supply-chain attack safeguards.
crowicrowi-review
Runs adversarial code reviews on git diffs using Codex with structured findings and selective fixes.
crowicrowi-kickoff
Automates worktree creation and agent session launch from approved implementation specs.
crowicrowi-qa
Runs bounded exploratory browser QA charters against Crowi dev worktrees via chrome-devtools MCP.
crowicrowi-handoff
Generates standardized HANDOFF documents, memory pointers, and notifications when pausing development sessions.
crowicrowi-design
Turns design ideas into reviewed RFCs or implementation-ready specs via multi-agent workflows.
crowicrowi-spec-review
Validates implementation specs adversarially against actual code using independent review lenses.
crowicrowi-role-planner
Initializes the planner role session by restoring inbox, specs, and role contracts.
crowicrowi-orchestrate
Orchestrates worktree integration, spec grooming, code review, and security alert monitoring per tick.
crowicrowi-release
Orchestrates Crowi releases through pre-flight checks, Go/No-Go decisions, and post-tag artifact verification.
crowicrowi-fix
Fixes bugs with a repro-first workflow, root-cause analysis, and a single-pass adversarial review.
crowicrowi-migration
Automate Crowi 2.0 migration from Express/Swig to Next.js and ts-rest.
Frequently Asked Questions About crowi
FAQPage SchemaWhat specific migration tasks does Crowi support?▼
Crowi enables the systematic transition of legacy wiki platforms from Express and Swig environments to Next.js. It focuses on modernizing the codebase by integrating ts-rest for robust, type-safe communication, ensuring data integrity and improved performance during the architectural shift from older server-side rendering patterns.
Which engineering personas benefit from this migration path?▼
Full-stack engineers and technical leads responsible for maintaining legacy wiki documentation systems benefit most. It is designed for developers tasked with reducing technical debt, improving maintainability, and upgrading outdated JavaScript stacks to current industry standards without losing existing wiki content or structural metadata.
What are the primary prerequisites for executing this migration?▼
Successful migration requires an existing Crowi 2.0 instance running on Express and Swig. Engineers must have a working knowledge of Next.js routing, TypeScript configuration, and the ability to map existing server-side endpoints to new ts-rest contract definitions to ensure full compatibility with the modernized architecture.