crane-code-style
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...
Découvrez les skills databases git workflows, comparez leurs dépôts et consultez leurs instructions.
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.
Steward repository documentation as a living, versioned knowledge graph focused on consistency, continuity, traceability, and controlled evolution; use when documentation changes cross-cut multiple artifacts, c...
Manage Git workflow for campaign content with proper commit messages and branching
Analyze git repository for insights: contributor stats, commit patterns, branch health, and change analysis. Outputs actionable reports.
Generate Git commit messages from staged changes using a conventional commit subject (English,
Code review for all uncommitted changes (staging status is irrelevant). Checks CLAUDE.md compliance, identifies bugs, security issues, style problems, and simplification opportunities.
Manage Git worktrees for isolated parallel development. Use when reviewing PRs, working on multiple features, or running autonomous loops without disturbing your main checkout.
Analyzes git changes to identify architectural decisions, infers context from source code analysis, and creates ADR files with minimal user input
Answers questions about GitHub repositories by cloning and analyzing them. Use when the user asks about GitHub repositories, needs code analysis, or wants to explore repository structure.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.