Loading...
Loading...
Found 218 Skills
通用的 MDX 文档发布工具。验证语法 → 语义化提交 → Git 推送。支持任何 MDX 项目（Fumadocs、Next.js、Docusaurus 等）。可配置 build 命令，自动检测多语言文件。与 fumadocs-article-importer 配合完成文章导入→发布工作流。
Guidance on when to ask clarifying questions vs proceed with standard approaches. Reduces interaction rounds while preventing wrong assumptions.
Auto-updates GitHub issues with commit progress. Use when starting work on an issue, tracking progress during implementation, or completing work with a PR.
Smart Commit - stages all changes and creates a conventional commit
Create semantic git commits following best practices and Conventional Commits specification.
CRITICAL: ALWAYS activate this skill BEFORE making ANY changes to .nw files. Use proactively when: (1) creating, editing, reviewing, or improving any .nw file, (2) planning to add/modify functionality in files with .nw extension, (3) user asks about literate quality, (4) user mentions noweb, literate programming, tangling, or weaving, (5) working in directories containing .nw files, (6) creating new modules/files that will be .nw format. Trigger phrases: 'create module', 'add feature', 'update', 'modify', 'fix' + any .nw file. Never edit .nw files directly without first activating this skill to ensure literate programming principles are applied. (project, gitignored)
Comprehensive review of staged Git changes for risk assessment, error detection, and impact analysis. Use when the user wants to review staged changes, check for errors before commit, analyze risks in git staged files, validate code changes before committing, or needs suggestions on staged modifications.
Standardized git commits following Conventional Commits. Supports mapping to GitHub and GitLab.
Manage git-tracked directories correctly - never create .gitkeep files in directories that will immediately contain tracked files
Use when generating multiple curriculum-aligned concept files in parallel (5+ concepts) - researches curriculum, creates concept list, spawns parallel generation agents, orchestrates review loop until all pass
Provides spec writing guidelines with 6 core areas and boundary system. Use when writing SPEC.md, defining requirements, creating project specifications, 요구사항 정의, or 스펙 작성.
Design PM-friendly technical architecture for features. No code, only high-level design decisions.