Loading...
Loading...
Found 65 Skills
Fetch project statistics from SpecStory Cloud. Run when user says "get project stats", "show SpecStory stats", "project statistics", "how many sessions", or "SpecStory metrics".
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Analyze your project and get personalized recommendations for Claude Code skills, MCP servers, and plugins
Instructions for working with sql-embedder generated files. Use when editing or working with .sql.ts files that contain the comment "This file was generated by sql-embedder". NEVER edit these generated files directly—edit the source .sql file and regenerate instead.
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when `ce-work` or `ce-code-review` offers a worktree option.
Opens a new jackin' feature or idea as a roadmap item draft plus an early pull request, without writing any code. Use when the operator runs /jackin-dev:propose.
Search GitHub for real-world code examples and implementation patterns. Use when user wants to find code examples on GitHub, search GitHub repositories, discover how others implement features, learn library usage patterns, or research architectural approaches. Fetches top results with smart ranking (stars, recency, language), extracts factual data (imports, syntax patterns, metrics), and returns clean markdown for analysis and pattern identification.
Manage logical workspaces for organizing development across multiple organizations/contexts. Use when: (1) Creating a new workspace for a project/org, (2) Listing available workspaces, (3) Switching active workspace, (4) Configuring workspace-specific settings (GitHub/JIRA tokens, work directory). Workspaces isolate configuration so you can work on personal projects vs work projects without conflicts.
Generates complete starter repositories for various tech stacks (Next.js, Vite, Nest, FastAPI, etc.) with best-practice conventions, folder structure, baseline code, configs, scripts, and setup documentation. Use when users request to "scaffold a project", "create a starter repo", "initialize a new project", or specify a tech stack to begin with.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Evaluate and validate Claude Code rules in .claude/rules/ directories. Use when auditing rule file quality, validating frontmatter and glob patterns, or checking rules organization before deployment. Do not use when writing new rules from scratch - use rule authoring guides instead. Do not use when evaluating skills or hooks - use skills-eval or hooks-eval instead.
Surfaces relevant instincts during work. Use when starting a task to check if any learned behaviors apply.