Git i control de versions
Operacions de Git, assistència per a commits i gestió de branques
github-tool
xuiltul
GitHub integration tool for listing and creating issues and PRs via the gh CLI wrapper. Use when: creating or listing issues or pull requests, or checking repository work on GitHub.
ring:finishing-a-development-branch
LerianStudio
Branch completion workflow - guides merge/PR/cleanup decisions after implementation is verified complete.
ring:using-git-worktrees
LerianStudio
Isolated workspace creation - creates git worktrees with smart directory selection and safety verification for parallel feature development.
ring:release-guide-info
LerianStudio
Generate Ops Update Guide from Git Diff. Produces internal Operations-facing update/migration guides based on git diff analysis. Supports STRICT_NO_TOUCH (default) and TEMP_CLONE_FOR_FRESH_REFS modes. Includes tag auto-detection and commit log analysis.
ring:brainstorming
LerianStudio
Socratic design refinement - transforms rough ideas into validated designs through structured questioning, alternative exploration, and incremental validation.
gh-cli
mfts
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
understanding-tauri-lifecycle-security
dchuk
Assists developers with understanding Tauri application lifecycle security threats spanning development, build, distribution, and runtime phases, including threat mitigation strategies and security best practices.
issue-auto-sync
jmagly
MCP tools: Gitea issue management
regression-bisect
jmagly
@.claude/agents/debugger.md
regression-auto-baseline
jmagly
@.claude/rules/executable-feedback.md - Executable feedback rules
regression-cicd-hooks
jmagly
@agentic/code/frameworks/sdlc-complete/agents/reliability-engineer.md
regression-performance
jmagly
@.claude/rules/executable-feedback.md - Execution validation requirements
zig-docs
NeverSight
Fetches Zig language and standard library documentation via CLI. Activates when needing Zig API details, std lib function signatures, or language reference content that isn't covered in zig-best-practices.
code-stats
NeverSight
"Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs). Get quick project overview without manual counting. Triggers on: how big is codebase, count lines of code, what languages, show semantic diff, compare files, code statistics."
git-best-practices
NeverSight
Git workflow patterns for commits, branching, PRs, and history management across heterogeneous repositories. Use when creating commits, managing branches, opening pull requests, or rewriting history. Do not use for non-git implementation tasks or repo-specific release policy decisions without repository documentation.
wechat-publisher
NeverSight
"一键发布 Markdown 到微信公众号草稿箱。基于 wenyan-cli，支持多主题、代码高亮、图片自动上传。"
commit
Adonis0123
Generate conventional commit messages with emoji prefixes from staged changes. Use when you need to draft, refine, or execute standardized commit messages quickly.
staged-review-validator
Adonis0123
Validate staged-changes-review findings with evidence-based verdicts and minimal-fix guidance. Use when you need to confirm whether each reported issue is valid and actionable.
infinitecampus-mcp
chrischall
This skill should be used when the user asks about Infinite Campus (Campus Parent) data for their student(s). Triggers on phrases like "check grades", "what's my kid's GPA", "any new assignments", "attendance record", "message the teacher", "Campus Parent inbox", "infinite campus", or any request involving school grades, assignments, attendance, messages, or documents in Infinite Campus.
weekly-report
Adonis0123
Generate structured weekly reports from Git commit history across one or multiple repositories. Use when you need concise, project-grouped progress summaries for status reporting.
work-issues
go-to-k
Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick as many FILE-DISJOINT issues as the run can carry, claim each on the issue before starting (collision-safe with other agents), verify against real AWS, then carry each through merge → pull → rebuild the linked binary → worktree cleanup. Use when asked to "handle/address filed issues", not to hunt for new bugs (that is /hunt-bugs).
run-integ
go-to-k
Run integration tests (deploy + destroy) against real AWS. Use when you need to verify cdkd works end-to-end with actual AWS resources.
create-pr
go-to-k
Run /verify-pr checks, then create a GitHub PR if all pass. Automates the full flow from quality checks to PR creation.
hunt-bugs
go-to-k
Proactively hunt for cdkd bugs by deploying real CDK apps that exercise common-but-untested AWS resources, configs, and CloudFormation notations against real AWS, then fix what breaks. Use for a periodic "find latent bugs" sweep, not for verifying a specific change.