Loading...
Loading...
Found 3,969 Skills
Implements a complete workflow for resolving GitHub issues directly from Claude Code. Guides through the full lifecycle from fetching issue details, analyzing requirements, implementing the solution, verifying correctness, performing code review, committing changes, and creating a pull request. Use when user asks to "resolve issue", "implement issue", "work on issue
Record git activity summary in memory log.
Set up automated CI failure detection and fixing using Claude Code. Use when you want to create a GitHub Actions workflow that automatically analyzes workflow failures, applies fixes for common issues, and opens issues for complex problems.
Download images from private GitHub issues and PRs using authenticated signed URLs.
Modern Git command best practices for AI agents. Use modern, purposeful commands introduced in Git 2.23+ instead of legacy multi-purpose commands. Teaches when to use `git switch` (branch operations), `git restore` (file operations), and other safer alternatives to improve clarity and reduce errors.
Navigate unfamiliar code using GitNexus knowledge graph
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, or create curated lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "repository name," "About section," "GitHub description," "GitHub topics," "GitHub Pages," "GitHub gist," "curated list," or "navigation list."
Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI.
Create GitHub PRs with structured title and body. Use when: opening PRs, creating pull requests after pushing. Triggers: /git-pr-create, create PR, open pull request.
This skill MUST be loaded on every git commit without exception. It should also be used when the user asks to "write a conventional commit", "format a commit message", "follow conventional commits spec", "create a semantic commit", "make a commit", "commit changes", or "git commit". Every commit message produced in this project MUST conform to this specification.
This skill should be used when the user asks to "create git hooks", "set up pre-commit hooks", "configure git hooks", "add commit validation", "implement pre-push hooks", or needs guidance on Git hooks implementation, validation scripts, or hook best practices.
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"