Draft and post a Connexity release announcement to Discord after cutting a CLI or platform release. Use this skill whenever the user types `/announce-release`, or asks to "announce the release", "post the release to Discord", "draft a release announcement", "tell Discord about the new version", "share the new release", or anything that sounds like wanting to publicise a freshly cut release of `connexity-cli` or the platform. Trigger even when the user just says something casual like "ok the release is out, let's tell people" — that's the intended use case. Do not trigger for non-release announcements (blog posts, hiring, generic Discord messages).
guidelines for creating forms with logic in separate hooks, server actions, and useMutation.
TanStack Query streaming with Next.js App Router - server prefetching, dehydration, Suspense boundaries, useSuspenseQuery/useSuspenseInfiniteQuery hydration pattern. Use when implementing data fetching that streams from server to client using TanStack React Query with Next.js RSC.
Use this skill whenever the user types /commit or asks to "commit changes", "make a commit", "commit my work", or similar. Reads the current git branch state, diffs against the target branch (pulling latest first), drafts a well-structured conventional commit message, confirms with the user before pushing. Never adds "Co-Authored-by" lines. Always follow this skill for any commit workflow — do not improvise a different approach.
Use this skill whenever the user types /create-pr, /pr, or asks to "open a PR", "create a pull request", "make a PR", "submit for review", or similar. If there are uncommitted changes, runs the /commit skill first. Then crafts a well-structured, detailed PR title and body, confirms with the user, and only then opens the PR via gh CLI. Never adds "Co-Authored-by" or any AI attribution. Always follow this skill for any PR creation workflow.
Use this skill whenever the user types /review-task-implementation or asks to "review the implementation", "check if the task was implemented correctly", "review PR changes against the Jira task", "does this PR implement the ticket", or similar. This skill fetches Jira task details and PR context (comments, conversations, review threads), then performs a structured review of the local branch changes against the requirements. Use this skill any time someone wants to validate that code changes satisfy a Jira ticket, even if they phrase it casually like "does this look right for CS-42" or "check my work against the ticket".