GitHub Repository Management
Clone/create/fork repos; manage remotes, releases.
Browse reusable instructions for your AI tools. Copy and customize a prompt, or download a skill for a supported agent.

Clone/create/fork repos; manage remotes, releases.
Commit, push, and create a PR for the current branch
Pragmatic coding standards - concise, direct, no over-engineering, no
Creates semantic atomic commits using Conventional Commits. Use always when committing changes, staging files, or when asked to commit code. Analyzes diffs, suggests scope, and can split changes into granular commits.
Automatically commits changes using conventional commits format (feat:, fix:, docs:, chore:, refactor:, test:, style:). Use after completing bug fixes, feature implementations, or documentation updates. Triggered automatically via Stop hook.
自動分析變更、生成 commit 訊息並提交。當使用者說「提交」、「commit」或要求提交變更時使用。
Clone and explore external codebases using the better-context CLI. Use this skill when: - User wants to explore a GitHub repository (e.g., "explore anthropics/claude-code") - User asks how a library/framework works and you need to read its source - User wants to understand implementation details ...
Specifies the usage of TODO comments to outline problems or bugs encountered in existing code, regardless of file type.
Guía definitiva para escribir código limpio, legible y mantenible según el Protocolo Antigravity.
Language-agnostic coding principles for high-quality, maintainable code. Apply when generating new code, reviewing existing code, or refactoring. Covers DRY, KISS, YAGNI, Fail Fast, avoiding over-validation, and generalized SOLID principles (SRP, DIP). Automatically detect violations and provide ...
Review code for Clean Code principles focusing on meaningful variable names, function length, and redundant comments. Use when the user requests code review with /review-code command, asks to check code quality, or wants to ensure code follows Clean Code principles. Supports JavaScript, Python, a...
Reimplement the current branch on a new branch with clean, narrative-quality git commit history suitable for reviewer comprehension. Use when you want to clean up messy commit history before opening a PR.
Generates semantic commit messages and commits code changes to version control. Use when staging changes, creating commits, writing commit messages, or when the user mentions git, commit, staging, or version control. Supports monorepo package updates tracking.
Assist with code review, refactoring, and explanations. Use when analyzing or improving code.
Use the VSCode CLI to open files at specific line and column positions when explaining code, debugging, pointing to TODOs, or guiding users to specific locations in files. Automatically invoked when Claude needs to show users exactly where in a file to look.
Provides expert guidance on writing maintainable code, focusing on readability, SOLID principles, and pragmatic coding practices.
Reviews code changes for bugs, style issues, and best practices. Use when looking for errors or improving code quality.
A skill for reviewing software changes. It helps analyze differences between git references (branches, tags, commits), review history, and provide feedback to ensure code quality and adherence to project conventions.
Skill for reviewing and analyzing code quality
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
This skill provides language-agnostic coding principles for maintainability, readability, and quality. Automatically loaded when implementing features, refactoring code, reviewing code quality, or when the user mentions "clean code", "best practices", "code quality", or "maintainability".
Universal coding principles and best practices for maintainable software
Try another platform, a broader search, or fewer filters.
Explore all resourcesResource formats: Prompts are ready to copy into a conversation. Skills install into the compatible agent shown on their page.
How it worksInclude the instructions, intended platforms, author, and license. Submissions are reviewed before publication.