Loading...
Loading...
Found 355 Skills
Orchestrate the 9-step skill development lifecycle for the CaldiaWorks Skills repository. Guides through ideation, issue creation, planning, branch creation, requirements definition, skill implementation, commit, pull request, and post-merge issue cleanup. Use when: skill development workflow, develop a skill end-to-end, skill-dev-workflow, /skill-dev-workflow, create and publish a skill.
Git-aware smart revert for tracks, phases, and tasks. Handles rewritten history, finds related commits, and provides safe rollback with multiple confirmation gates.
Automate Gitcode Pull Request creation workflow for OpenHarmony graphic subsystem including code commit, issue creation, and PR submission with proper template formatting. Use when user needs to create a PR for the Gitcode platform, especially for OpenHarmony graphic projects that require specific PR templates with CodeCheck tables and Signed-off-by tags.
Prepare branch for code review by building context, identifying issues, and suggesting improvements
UPDATE-DOCS phase. Refresh README.md, CLAUDE.md, and docs/index.html to reflect changes made this session. Commits and pushes doc updates. Terminal phase — declares COMPLETE.
Initialize a new project — repo, structure, CI, and first commit
Sync the local main branch with the latest code from the official upstream or origin remote
Create a traceable Git branch for the current task.
This skill should be used when the user wants to create a pull request, or submit code for review. Triggers on "push a PR", "create a PR", "open a pull request", "make a PR", "submit for review".
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
AntiGravity Start Work/Finish Work/New Project Initialization Process. Loaded when saying 'Start Work', 'Finish Work', or 'Initialize Project'.
Crear un proyecto nuevo fusionando una plantilla del equipo según el stack tecnológico (Angular, React, Symfony, etc.). Usar siempre que el usuario pida crear un proyecto nuevo, inicializar desde plantilla, o use `/project-create`. Si el stack no está claro, preguntar antes de cualquier acción.