self-updating
How cc-prime automatically stays current with Claude Code evolution. Use when discussing showcase maintenance, documentation sync, or keeping the showcase updated.
Discover blockchain git workflows skills, compare source repositories and read the instructions for each workflow.
How cc-prime automatically stays current with Claude Code evolution. Use when discussing showcase maintenance, documentation sync, or keeping the showcase updated.
Sub skill for pbt-workflow-guide. Apply Aletheia to generate and sync PBT templates/tests for any non-aletheia MoonBit repo.
Follow Git best practices for commits, branching, and collaboration. Use this skill when creating commits, managing branches, resolving merge conflicts, or establishing Git workflows for teams.
Git workflow automation for creating feature branches, committing, pushing, merging to main, and pushing main. Use when asked to do git branch/commit/push/merge steps or "one command" release.
Drift-sync governance workflow for keeping SSOT instructions aligned with codebase reality. Use when conventions change, repeated review comments indicate hidden rules, or codebase behavior diverges from docume...
Documentation synchronization knowledge. Use when analyzing documentation patterns, understanding how code changes map to documentation needs, or determining documentation structure for different project types.
This skill should be used when the user asks about "code style", "naming convention", "imports", "section headers", "slot naming", "viaIR", "stack too deep", "formatting", or needs guidance on Crane's code conv...
Update GitHub PR descriptions with AI session export summaries. Use when user asks to add session summary to PR, document AI assistance in PR, or export conversation summary to PR description.
This skill reviews the current chat session and GitHub Copilot instructions to identify user-reported issues that should become new lessons, detect violations of existing instructions, and update instructions a...
Expert on complex Git operations, recovery, and repo hygiene.
Team progress management with development planning, risk control, and progress tracking. Use when managing multi-person projects, tracking task ownership, or coordinating branch workflows.
Create GitHub Copilot instruction files with proper applyTo patterns and prescriptive rules. Use when asked to "create instruction", "make instruction", "scaffold instruction", or when building file-type-specif...
Break down high-level plans into specific tasks with file paths, line numbers, and verification steps. Creates execution-ready implementation plans.
GitHub deployment operations for Everest Capital projects. Includes automated git operations, GitHub Actions workflow triggers, Cloudflare Pages deployment, and post-deploy verification. Repos include brevard-b...
CI/CD pipeline design, GitHub Actions, and deployment automation. Auto-triggers when setting up pipelines, automating deployments, or configuring workflows.
This skill should be used when the user asks to "finalize", "/finalize", "ship it", "ship this", "wrap up", "wrap this up", or "finish and commit". Orchestrates the complete workflow for finishing development w...
Creates GitHub Actions CI/CD workflows for testing, building, and deploying applications. Supports Nix/devenv builds, container publishing, and multi-environment deployments. Use when setting up CI pipelines, r...
Continuous integration and deployment with GitHub Actions
Configure a repo's agent instruction files (AGENTS.md, CLAUDE.md, etc.) to auto-apply Devvit skill guidance. Trigger phrases: "configure skills", "setup skills", "add devvit docs rule".
This skill should be used when the user asks about "code style", "naming convention", "imports", "section headers", "slot naming", "viaIR", "stack too deep", "formatting", or needs guidance on Crane's code conv...
Documents codebase structure and implementation without evaluation or recommendations.
Reviews code changes in the Nick Stack codebase, checking for tech stack patterns, security, type safety, and best practices. Use when reviewing PRs, commits, or code changes.
Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
Ensure consistent code quality, style, and best practices for mobile apps. Use when writing code, reviewing PRs, or setting up linting.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.