hirogakatageri
29 verified skills93 total stars
verify-and-fix
This skill should be used when the user reports an error, bug, or unexpected behavior and wants it diagnosed and fixed. Trigger on phrases like "check this error", "check this bug", "here's an error", "here's a bug", "I have an error", "I have a bug", "found a bug", "got an error", "debug this", "this is broken", "fix this error", "verify and fix", or any message that includes a stack trace or error output. Runs a structured workflow: gather context, investigate configured log/code sources, report root cause with ranked solutions, then apply a test-driven fix.
development5
svelte-env-vars-check
This skill should be used when the user says "check svelte env vars", "check environment variables", "validate env vars", "check env var patterns", "audit environment variables", "audit env vars", "check SvelteKit env", "svelte env check", or any phrase asking to audit or validate SvelteKit environment variable usage patterns.
testing5
check-in
This skill should be used when the user says "check in", "clock in", "standup", "guild check in", "what's the status", "let's get to work", "start working", "daily standup", "guild standup", "I'm here", "reporting in", or any phrase indicating they want to begin or resume a guild work session. Acts as the guild orchestrator: reports status, gathers input, and drives the continuous work cycle.
testing5
create-workflow
This skill should be used when the user asks to "create a workflow", "generate a workflow", "add a GitHub Actions workflow", "create a CI/CD pipeline", "write a script workflow", "automate a task", "set up automation", or wants to build any kind of automated workflow (GitHub Actions, Python scripts, Node.js scripts, shell scripts, Makefiles, etc.). Interactively gathers goals and configuration, suggests file names, job names, and step names, then generates a complete ready-to-use workflow file.
tools5
end-session
This skill should be used when the user says "end session", "wrap up", "I'm done for today", "close the session", "session complete", "log off", "signing off", "finish the session", "that's it for today", "done for now", "calling it a day", "let's wrap up", "save the session", "session summary", or any phrase indicating they are ending or wrapping up their current work session. Spawns the session-tracker:logger agent to record the session.
data-ai5
query-changes
Internal skill used by the session-tracker logger agent to query git for committed and uncommitted changes in the past 28 hours. Not user-invocable.
data-ai5
save-log
Internal skill used by the session-tracker logger agent to append a session entry to .logs/YYYY-MM-DD-log.md, creating the file and directory if needed. Not user-invocable.
data-ai5
daily-summary
This skill should be used when the user says "daily summary", "summarize today", "generate daily summary", "what did I do today", "today's summary", "daily report", "summarize all projects today", or any phrase asking for a summary of all work done across projects today. Searches all subdirectories for .logs/YYYY-MM-DD-log.md files, summarizes each project's sessions, and saves a grouped report to .logs/YYYY-MM-DD-daily-summary.md.
data-ai5
discuss
This skill should be used when the user says "discuss", "let's discuss", "discuss [topic]", "talk about", "let's talk about", "summarize the context", "what are we working on", "break down the topics", "what subjects do we have", "let's review the context", "recap the conversation", or any phrase asking to analyze and discuss the current context or a specific subject within it.
testing5
svelte-best-practices
Pre-loaded Svelte 5 / SvelteKit best practices for the developer-svelte agent. Covers state management strategies, performance optimization, accessibility, SEO, TypeScript usage, testing (vitest + playwright), and error handling. Load alongside the other svelte-* skills before implementing anything non-trivial. Trigger phrases include "svelte best practices", "svelte performance", "svelte accessibility", "svelte typescript", "svelte testing", "sveltekit seo", "sveltekit error handling".
development4
svelte-advanced
Pre-loaded advanced Svelte 5 / SvelteKit techniques for the developer-svelte agent. Covers attachments ({@attach}), actions (use:), transitions and animations, the motion module, custom elements, packaging libraries, server hooks, remote functions, service workers, shallow routing, and view transitions. Load when the task involves animation, dom integration, library packaging, advanced data flow, or pwa features. Trigger phrases include "svelte transition", "svelte animation", "svelte attachment", "svelte action", "remote function", "shallow routing", "service worker", "custom element".
development4
svelte-build-deploy
Pre-loaded SvelteKit knowledge for the developer-svelte agent. Covers project structure, file-based routing (+page, +layout, +server, +error), load functions (universal vs server), form actions, page options (prerender / ssr / csr), building for production, and deployment via adapters (auto, node, static, vercel, cloudflare, netlify). Load this skill before working on any SvelteKit route, server module, or build configuration. Trigger phrases include "sveltekit routing", "+page", "+server", "load function", "form actions", "sveltekit adapter", "svelte deploy".
development4
svelte-core
Pre-loaded Svelte 5 core knowledge for the developer-svelte agent. Covers the component model, runes ($state, $derived, $effect, $props, $bindable), basic markup, control flow, snippets, bindings, scoped styles, lifecycle, and context. Load this skill before writing or editing any .svelte, .svelte.ts, or .svelte.js file. Trigger phrases include "svelte core", "svelte runes", "svelte 5 component", "svelte state", "svelte derived", "svelte effect", "svelte props", "svelte bind".
development4
clear-board
This skill should be used when the user asks to "clear the board", "reset the guild", "start fresh", "wipe the board", "clear all tasks", "reset the board", or wants to remove all current work from the guild board and start over.
tools2
develop-project
This skill should be used when the user asks to "develop a project", "implement requirements", "build from requirements", "start a project from requirements", "turn my requirements into code", "build my app from my spec", "implement my app from this document", "scaffold from requirements", "I have a requirements doc and want to start coding", "I have a spec and want to start building", "full requirements-to-implementation workflow", "build project using phases", "resume my project build", "continue my interrupted build", or "my build was interrupted". Transforms a requirements document into a fully implemented, phase-structured codebase using automated planning and parallel execution across 8 clean architecture phases.
development2
comprehensive-review
Use this skill when the user wants to review code changes, verify implementation quality, or check readiness before a PR or deployment. Trigger on phrases like "review my changes", "run comprehensive review", "check all my code", "am I ready for PR", "before I create a PR", "before I merge", "code audit", "quality check", "verify my implementation", "is my feature complete", "run all reviewers", "check if my implementation is complete", "deep code review", "deep review", or any multi-dimensional code analysis request. Also use proactively when the user says they've finished a phase, completed a feature, or are wrapping up work — even if they don't explicitly ask for a "review". Covers requirements compliance, test coverage, edge cases, architecture alignment, and security.
development2
generate-requirements
This skill should be used when the user asks to "generate requirements", "create requirements", "write requirements", "define requirements", "document requirements", "requirements for feature", or wants to transform ideas into structured requirements documents. Launches the product-owner agent to gather requirements and outputs a single requirements file in a requirements/ folder.
documentation2
conventional-commit
This skill should be used when the user asks to "create a conventional commit", "generate conventional commits", "generate commit", "commit with conventional format", "group my changes for commits", "make a conventional commit message", or mentions "semantic commits", "commitizen", "commit conventions". Analyzes staged and unstaged changes, groups related modifications, and generates properly formatted conventional commit messages with interactive commit grouping options.
development2
list-request-monitoring
This skill should be used when the user asks to "list request monitoring", "show monitoring jobs", "what monitoring is running", "show active schedules", "list cron jobs", or "what's scheduled". Lists all active request monitoring cron jobs in the current session.
tools2
categorize-task
Reference guide for classifying development tasks into the 8-phase clean architecture structure (Foundational → Models → Services → Data → Rules → State Management → UI → Tests). Use when you need to determine which architectural phase a task belongs to.
development2
create-request
This skill should be used when the user asks to "create a request", "add a request", "queue a request", "submit a request", "new request", or "make a request for the orchestrator". Creates a structured request file in requests/todo/ that the Project Orchestrator can pick up and execute.
tools2
split-plan
Analyze a master plan file and split it into 8 phase-specific implementation plans organized by feature tracks. Automatically identifies tracks, classifies tasks by phase, scores complexity, and generates detailed phase plan files following clean architecture principles.
testing2
start-request-monitoring
This skill should be used when the user asks to "start request monitoring", "monitor requests", "watch requests", "start watching for requests", "auto-process requests", "check requests every hour", or "start the orchestrator on a schedule". Schedules the Project Orchestrator to automatically check requests/todo/ every hour and process any pending request files.
testing2
comprehensive-review
Use this skill when the user wants to review code changes, verify implementation quality, or check readiness before a PR or deployment. Trigger on phrases like "review my changes", "run comprehensive review", "check all my code", "am I ready for PR", "before I create a PR", "before I merge", "code audit", "quality check", "verify my implementation", "is my feature complete", "run all reviewers", "check if my implementation is complete", "deep code review", "deep review", or any multi-dimensional code analysis request. Also use proactively when the user says they've finished a phase, completed a feature, or are wrapping up work — even if they don't explicitly ask for a "review". Covers requirements compliance, test coverage, edge cases, architecture alignment, and security.
development2
stop-request-monitoring
This skill should be used when the user asks to "stop request monitoring", "stop watching requests", "cancel request monitoring", "stop the orchestrator schedule", or "stop-request-monitoring {job-id}". Cancels the hourly request monitoring cron job that was started by start-request-monitoring.
tools2
initialize-project
This skill should be used when the user asks to "initialize project", "set up project", "init project", "create project structure", "prepare project folders", or "set up workspace". Creates the standard project directory structure with folders for requirements, tasks, and requests.
tools2
guild-status
This skill should be used when the user asks for "guild status", "board status", "show the board", "what's on the board", "project status", "show guild", "guild board", or "what's happening". Shows a quick read-only view of the guild board without starting the work cycle.
tools2
new-requirement
This skill should be used when the user asks to "add a requirement", "new requirement", "I need a feature", "add to the guild", "create requirement", "queue a feature", "I want to build", or wants to add a new work item to the guild board. Creates a requirement stub and a product-owner task to gather the full details.
development2
release
This skill should be used when the user asks to "cut a release", "release the guild", "ship it", "create a release", "tag a version", "publish a release", "guild release", or wants to finalize completed requirements into a versioned release. Renames CHANGELOG Unreleased to a version, archives completed REQs, and creates an annotated git tag. Does not push.
documentation2