่ฐ็ ๆฅๅ็ฝ้กตๅๅธๅทฅไฝๆตใ็จไบๅฐ่ฐ็ ๅ ๅฎนๅๅธไธบๅฏๅจ็บฟๆฅ็็HTML็ฝ้กต๏ผๅนถๆจ้ๅฐGitHub็ๆๅฝๅ ๅฏ่ฎฟ้ฎ็้ๅ้พๆฅใ่งฆๅๅบๆฏ๏ผ(1) ็จๆท่ฆๆฑๅๅธ่ฐ็ ๆฅๅ (2) ้่ฆๅฐHTML้จ็ฝฒๅฐ็บฟไธ (3) ้่ฆ็ๆๅฝๅ ๅฏ่ฎฟ้ฎ็้พๆฅ (4) ๅฎๆไปๅ ๅฎนๅฐ็ฝ้กตๅๅธ็ๅฎๆดๆต็จ (5) ็จๆทๅ้"็ ็ฉถ"ใ"่ฐ็ "ใ"ๅๆ"ใ"ๆต่ฏ"ใ"ๅฏนๆฏ"ใ"ๆฅๅ"็ญๅ ณ้ฎ่ฏๆถ่ชๅจ่งฆๅ
Orchestrates software development by coordinating with Cursor Agent, managing git workflows, and ensuring quality delivery. Use when implementing development requirements, feature requests, bug fixes, or refactoring tasks that involve git operations, build verification, and deployment pipelines.
issue-to-pr โ Automatically fix GitHub issues end-to-end: reads the issue, analyzes repository code, implements a fix, and submits a pull request. Use when the user provides a GitHub issue URL, mentions fixing a GitHub issue, or uses the /fix-issue command. Supports URLs in the format https://github.com/{owner}/{repo}/issues/{number}.
่งๅๆฌๅฐ็ฅ่ฏๅบ็็ฎๅฝใๅ็็ฒๅบฆใๅฝๅใๆดๆฐๆถ้ดไธ่ฎฟ้ฎ่พน็๏ผ่ไธๆฏ็ดๆฅๅ RAGใ๏ผuse for rag, indexing, knowledge workflows๏ผdo not use for ็ดๆฅ้จ็ฝฒๅ้ๆฐๆฎๅบ, ๅฟฝ็ฅๆ้้็ฆป.
ๆซๆไปๅบ็ฎๅฝไธ่ฏดๆๆไปถ๏ผ็ๆๆฐๆๅไธๆ่ทฏๅพใๆจ่้ ่ฏป้กบๅบไธ่ธฉๅๆ้ใ๏ผuse for repo, onboarding, developer-experience workflows๏ผdo not use for ๆณๆผ็งๆๆบ็ ๅ ๅฎนๅฐๅค้จ, ๆง่กๆๅปบๅฝไปค.
ๆฏๆฅ่ชๅจ่ทๅ GitHub Trending ็ญ้จ้กน็ฎ๏ผๆจ้้็ฅใๆฏๆ่ชๅฎไน่ฏญ่จใๆถ้ด่ๅดใๆจ้ๆธ ้๏ผTelegram/้้/ไผไธๅพฎไฟก๏ผใ้ถๆๆฌ่ฟ่กใ
Track GitHub repo growth (stars, forks, issues, commits) with periodic digests and trend analysis. Compare your repos against a watchlist. Use when checking repo stats, monitoring growth, setting up a github digest, comparing repos, or managing a repo watchlist. Requires GITHUB_TOKEN environment variable or GitHub PAT (see Credentials).
Read, explain, and evaluate a software repository or GitHub project in an engineering-oriented way. Use when the user asks to read a repo, understand a codebase, analyze architecture, evaluate whether a project is worth following or adopting, prepare onboarding notes, or summarize stack, module boundaries, risks, and entry points. Supports three output modes: ้่ฏป็, ๆถๆ็, and ๆฅๆ่ฏๅฎก็. Also supports a lightweight GitHub health layer for public repositories when the user asks whether a project is worth following, adopting, or referencing. Triggers include requests like ่ฏปไธไธ่ฟไธช้กน็ฎ, ็็่ฟไธช GitHub ไปๅบ, ๅๆไธไธ repo, ่ฟไธช้กน็ฎๆไนๆ ท, ๅธฎๆๅฟซ้็่งฃไปฃ็ ็ปๆ, ็ปๆไธไธชๆถๆๅๆ, or ็ปๆไธไธชๆฅๆ่ฏๅฎก.
Essential Git commands and workflows for version control, branching, and collaboration.
Review the current conversation context and git changes, then persist durable repository knowledge into `docs/*.md` by domain and into `AGENTS.md` for cross-cutting repo rules. Use after features, fixes, refactors, architecture changes, schema changes, or when the user mentions docs, documentation, design, architecture, business logic, conventions, or `AGENTS.md`.
Installing dependencies, running dev/build/test/lint, filtering packages, single-test runs, git hooks, preparing a clone (.env.development / .env.test), or Docker-backed local services and dev servers.
GitHub issue comment guidelines for community interaction. Use when responding to GitHub issues, bug reports, feature requests, or any GitHub discussion.
Provides comprehensive guidelines for resolving merge conflicts intelligently using git history and commit context. Use when tasks involve merge conflicts, rebasing, PR conflicts, or git conflict resolution. This skill analyzes commit messages, git blame, and code intent to make intelligent resolution decisions.
Review code changes in Memgraph's storage layer, including MVCC, concurrency patterns, WAL, recovery, DDL operations, index/constraint management, delta chains, and skip list operations. Invoke for pull requests or changes to src/storage/v2/.
Workflow for merging a DevTools submodule into its parent module. Covers BUILD.gn consolidation and updating devtools_grd_files.gni.
Use when managing branches, creating and uploading CLs, or handling stacked changes in the DevTools Gerrit-based workflow.
Migrate TypeScript library projects from tsup to tsdown. Provides complete option mappings, config transformation rules, default value differences, and unsupported option alternatives so AI agents can intelligently perform migrations.
Use when triaging a GitHub issue - analyzes issue, checks for duplicates, categorizes, and drafts response
Manages GitHub issue and pull-request lifecycle including creation, updates, triage labelling, and closeout metadata using canonical templates and repository taxonomy. Use when a maintainer asks to create, update, close, or triage GitHub issues or PRs, or when issue creation requires codebase analysis for scope, labels, or acceptance criteria.
Update the body of a GitHub pull request. Use when the user asks to update, edit, or modify a PR description/body.
