Loading...
Loading...
Found 356 Skills
Create a pull request with Conventional Commits formatting, a templated body, and local verification. Use when the user asks to create a PR, open a PR, submit changes for review, or put code up for review.
Use when writing, generating, or drafting a pull request description. Always use this skill when the user asks to "write a PR description", "create a PR", "draft a pull request", "generate PR text", or similar. Produces a complete, structured PR description following the team's conventions: ticket-key title, Purpose, Approach with implementation details, and a Pre-Review Checklist.
Use when executing a claimed Nexus task. Creates zr-workspace/ structure with reference clones in zenon-red/ and forked work repos in <username>/.
Use this skill whenever the user wants to build, scaffold, modify, debug, or ship a web application, including React/Vite/Next.js/Vue/Svelte apps, full-stack prototypes, dashboards, landing pages with interactivity, games, admin panels, CRUD apps, API-backed UIs, authentication flows, database-connected apps, or when they say things like "build a web app", "make a frontend", "create a SaaS prototype", "turn this idea into an app", "搭建 Web 应用", "做一个网站应用", or "帮我开发前端". This skill should trigger even if the user does not explicitly mention a framework, because it guides framework selection, project structure, implementation, testing, live preview, and Git commits after each working slice.
Review local code changes organized into logical chapters with Stage CLI, a code review tool that works with any AI agent
Work with Git repositories from the command line.
Use when creating a GitHub pull request or merge request from the current branch, especially when a project PR template may exist.
Cerrar e integrar el trabajo de una historia de usuario haciendo merge de la rama feature/US-XXX hacia la rama desde la que se creó, previa verificación de que progress.md tenga todas las tareas en Done. Activar cuando el usuario pida cerrar, entregar, mergear, integrar, finalizar o hacer submit del trabajo de una historia, una US o de la rama actual.
Resolve git merge, rebase, or cherry-pick conflicts via a structural-merge cascade — mergiraf (AST-aware auto-resolve) → git rerere (replay remembered fixes) → kdiff3 (manual fallback). Use when conflicts exist and the user wants them resolved — phrases like "melt the conflicts", "fix the merge conflicts", "resolve the rebase conflicts", "what's conflicting after the merge", "/melt", "fix the cherry-pick", or any prompt that surfaces `<<<<<<<` markers, `CONFLICT (...)` git output, or a half-finished merge state. Use even when only one file is conflicting if the user wants the structural pass attempted before manual editing. Do NOT use for general git operations without conflicts. After `/cook` or `/cure` if a merge step blocked them; before retrying the gate that surfaced the conflict.
Distills a completed deep-plan document (e.g. docs/PLAN.md) into durable project knowledge files: AGENTS.md (agent operating rules and verified ground truth), docs/ARCHITECTURE.md (component map, data flow, framework mechanisms with citations), and ROADMAP.md (phased roadmap with live status). Carries only VERIFIED evidence forward, re-checks stale claims, and merges into existing files instead of overwriting. Use after a deep-plan finishes, when the user mentions deep-plan-ingest or ingest the plan, or asks to generate/update AGENTS.md, ARCHITECTURE.md, or ROADMAP.md from a plan.
Creates GitHub pull requests with properly formatted titles. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request. Analyzes changes on the current branch and uses the pull request template from .github folder.
Create standardized git commit messages. Prioritize following the project's existing commit conventions, and support the Conventional Commits format. Usage scenarios: Users request to create commits or write commit messages