collaborative-progress
Team progress management with development planning, risk control, and progress tracking. Use when managing multi-person projects, tracking task ownership, or coordinating branch workflows.
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
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...
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.
Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
Core execution workflow - Plan, Execute, Verify, Commit cycle for autonomous development
Complete feature development workflow from spec to delivery with review and testing
Provides architectural guidance and design patterns for implementing new features in the Nick Stack codebase. Use when planning implementations, designing new features, or making architectural decisions.
Guidelines for establishing and maintaining a standardized, intuitive, and automated repository environment to minimize technical debt and ensure long-term maintainability.
Tracks, classifies, and prioritizes technical debt (code, spec, and process) over time. Use to prevent silent rot.
Provides architectural guidance and design patterns for implementing new features in the Nick Stack codebase. Use when planning implementations, designing new features, or making architectural decisions.
Guide for creating DevContainer features. Use when creating a new feature for devcontainer, implementing install.sh scripts (npm package, binary download, source build, dotnet tool, or directory setup patterns)...
Analyzes problems, researches the codebase, asks clarifying questions, and creates step-by-step implementation plans stored in .github/upgrades/ folder for other models to follow.
Review and update MkDocs documentation when code changes. This skill should be used when completing feature implementation, after making code changes that affect user-facing functionality, when reviewing PRs fo...
Triage build and CI failures with a focus on fixing errors quickly using minimal diffs. Use when the build fails locally or in CI.
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.