代码评审
自动化代码审查与分析
frontend-ui-animator
julianromli
Analyze and implement purposeful UI animations for Next.js + Tailwind + React projects. Use when user asks to add animations, enhance UI motion, animate pages/components, or improve visual feedback. Triggers on "add animations", "animate UI", "motion design", "hover effects", "scroll animations", "page transitions", "micro-interactions".
code-debugging
lingzhi227
Debug experiment code with structured error analysis. Categorize errors, apply targeted fixes with retry logic, and use reflection to prevent recurring issues. Use when experiment code fails or produces incorrect results.
git-workflow
netresearch
"Use when establishing branching strategies, implementing Conventional Commits, creating or reviewing PRs, managing PR review threads, merging PRs with signed commits, handling merge conflicts, or integrating Git with CI/CD."
github-pr
Gentleman-Programming
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
Final Review - Comprehensive PR Review & Testing
nicknisi
Be honest: "This pass was substantial - I'd recommend one more review" or "Changes were minimal - ready to merge"
content-strategy
Logos-Liber
Documentation architecture, content planning, and maintenance strategies
hero-story
SimHacker
Safe referencing of real people's traditions without impersonation
github
SimHacker
See also: tmnn7-8/github-simulation for GitHub as MMORPG
action-queue
SimHacker
Sims-inspired task scheduling â queue actions, execute in order
evaluator
SimHacker
Independent assessment without debate context — adversarial loop prevents gaming
context
SimHacker
Runtime context passed to compiled closures — the world as seen from inside
code-review
SimHacker
Systematic code analysis with evidence collection
advertisement
SimHacker
Objects announce what they can do — The Sims style
cursor-mirror
SimHacker
MOOLLM
bartender
SimHacker
Generic bartending capabilities â pour drinks, manage tabs, know regulars
codebase-documenter
travisjneuman
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.
pr-workflow
markus41
Comprehensive knowledge for creating, managing, and merging pull requests with Jira integration, following best practices for code review, deployment, and team collaboration
harness-mcp
markus41
Harness MCP (Model Context Protocol) server integration for AI-powered CD operations, pipeline management, Git repositories, pull requests, code review comments, and bidirectional Jira synchronization
Jira Orchestration Workflow
markus41
This skill should be used when the user asks to "orchestrate jira", "work on issue", "complete jira ticket", "development workflow", "jira automation", "issue lifecycle", "work on story", "fix bug ticket", or needs guidance on coordinating development work through Jira with multi-agent orchestration patterns.
manager-orchestration
markus41
Establishes manager-level coordination contracts and cross-domain handoffs.
task-details
markus41
Enriches Jira tasks with comprehensive context, requirements analysis, and technical details through intelligent extraction, dependency mapping, and historical analysis
generate-test-cases
clear-solutions
Analyze code and generate a structured list of test cases following battle-tested INCLUDE/EXCLUDE rules. Outputs Given-When-Then format covering all code branches. Use before writing actual tests.
minimalist-review
slavingia
Review any business decision, plan, or strategy through the minimalist entrepreneur lens. Use when someone wants a gut-check on a business decision, wants to simplify their approach, or needs to decide between options.
hai-architecture
hylarucoder
Produce an evidence-grounded architecture review or design-decision critique — an architecture map, the painful complexity center, 3-6 chosen review lenses, ranked findings with file:line evidence, why-not alternatives, and a red/blue adversarial check — grounded in John Ousterhout's "A Philosophy of Software Design" (APoSD). Trigger whenever the user asks about architecture or system-design quality: module/package boundaries, abstraction depth, deep vs shallow modules, information hiding, dependency direction, change amplification / blast radius, ownership, error boundaries, or whether to split / merge / combine modules — including 架构审查, 架构 review, 模块边界, 依赖方向, 抽象太浅, 复杂度太高, 这个设计合不合理, or an APoSD / Ousterhout / "philosophy of software design" review. Be pushy: trigger even when they only say "is this structure ok", "these modules feel tangled", "should I split this", "review my system design", or "why does touching X force edits everywhere", not just when they say "architecture review". For naming use hai-naming; for whole-repo refactor hunting use improve-codebase-architecture; for a single React component use component-diagnosis.