push-pr
Push branch and create GitHub PR
Découvrez les skills tools git workflows, comparez leurs dépôts et consultez leurs instructions.
Push branch and create GitHub PR
Fetch Linear issue and create branch
Standards for commit messages and version control.
Rules for file organization, naming conventions, and environment variables.
Trim large tool outputs to free context space
Perform a comprehensive code review of current uncommitted changes in a git repository. Analyzes for bugs, security vulnerabilities, best practices, DRY violations, code smells, performance issues, and areas of...
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Automated privacy review for git repositories. Scans for sensitive data exposure including API keys, passwords, database credentials, and tokens. Use before pushing to public repositories or sharing code. Trigg...
Jujutsu (jj) version control commands. Use when working in a jj repository, running version control operations, viewing commit history, managing bookmarks (branches), creating or splitting commits, pushing to...
Automate and inspect GitHub Actions runs with the asim-utilities Python library/CLI. Use when triggering workflows, listing recent runs or failures, waiting/canceling runs on job failure, or downloading run log...
Git conventions - commit messages, branch management, rebasing. Use when committing code or reviewing commit history.
Enforce repo execution discipline: keep PRs small; run migration-smoke when invariants change; never hand-edit vendored contracts.
This skill should be used to remove AI-generated artifacts and unnecessary code before committing. It scans changed files for redundant comments, AI TODOs, excessive docstrings, and unnecessary markdown files....
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness dates
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...
完整功能開發工作流程 - 代碼審查→代碼簡化與修正→知識管理→Git推送。階段一發現問題,階段二自動修正🔴高嚴重度問題並簡化代碼,最後自動 commit & push
Automatically generate conventional commit messages when user has staged changes and mentions committing. Analyzes git diff and status to create properly formatted commit messages following conventional commits...
Orchestrates full feature development workflow from discovery through commit. Infers scope from feature description and adapts phases accordingly. Use when adding any new feature, regardless of size.
Creates pull requests with smart defaults. Infers target branch from branch name, adapts description detail to PR size, and runs appropriate checks based on PR type (draft vs final). Use when ready to open a PR...
Keeps OpenEvent-AI “living docs” in sync while coding. Use whenever you fix a bug, discover a new bug, add/modify behavior, or capture a future idea. Updates docs/guides/TEAM_GUIDE.md (bug list + regressions),...
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é.