Loading...
Loading...
Found 1,617 Skills
Use when the user wants to update, refresh, or reinstall the CopilotKit agent SKILLS (the SKILL.md files that teach this agent about CopilotKit). NOT for updating the CopilotKit codebase or project — this is specifically about refreshing the skills/knowledge this agent has loaded. Triggers on "update copilotkit skills", "update skills", "refresh skills", "skills are stale", "skills are outdated", "get latest skills", "my copilotkit knowledge is wrong", "copilotkit APIs changed", "skills seem old", "wrong API names", "reinstall skills", "skills not working right", "update your copilotkit knowledge".
Summarize recent compound-engineering plugin releases, or answer a specific question about a past release with a version citation. Use when the user types `/ce-release-notes` or asks "what changed in compound-engineering recently?" or "what happened to `<skill-name>`?".
Clone/create/fork repos; manage remotes, releases.
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
GitHub PR의 미해결 리뷰 스레드를 조회해 코멘트별로 타당성을 검증한 뒤, 적절한 지적만 골라 수정·커밋한다. 모든 리뷰어(봇·사람)의 코멘트를 처리한다. "코드 리뷰 반영해줘", "리뷰 코멘트 처리해줘", "PR 리뷰 적용해줘", "apply PR review comments", "handle review feedback", "autofix", "/autofix" 같은 요청에 활성화한다. 리뷰 코멘트를 그대로 적용하지 않고, 검증에서 적절로 판정된 것만 사용자 승인(기본) 또는 자동(`--auto`)으로 반영한다.
Initialize a new project with deep context gathering and project.md. Triggers include "new project", "start project", "initialize project", "create project", "begin project", "setup project".
Validate and fix GFM links in PR descriptions. TRIGGERS - PR links, gh pr create, GFM validation, broken PR links.
Configures release-please for monorepos and single-package repos. Handles manifest files, component tagging, changelog sections, and extra-files setup. Use when setting up automated releases, fixing release workflow issues, or configuring version bump automation.
Enterprise template management with code boilerplates, feedback templates, and project optimization workflows
Publish @autumnsgrove/groveengine to npm with proper registry swap workflow. Use when releasing a new version of the engine package to npm.
Interactive conversation to resolve [NEEDS CLARIFICATION] markers using /speckit.clarify command. Claude asks questions about missing features, UX/UI details, behavior, and priorities. Updates specs in .specify/memory/ with answers to create complete, unambiguous documentation. This is Step 5 of 6 in the reverse engineering process.
Take a list of projects and their related documentation, and organize them into the SRED format for submission.