Topic: github
107 skills in this topic.
-
hetzner-deploy
This skill should be used when user asks to "deploy to Hetzner", "create Hetzner server", "manage Hetzner Cloud", "hcloud CLI", or works with Hetzner Cloud infrastructure including servers, networks, firewalls, load balancers, DNS zones, and volumes.
fcakyon/claude-codex-settings 589
-
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
fcakyon/claude-codex-settings 589
-
pdf
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
fcakyon/claude-codex-settings 589
-
docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
fcakyon/claude-codex-settings 589
-
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
yusufkaraaslan/Skill_Seekers 12,654
-
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
yusufkaraaslan/Skill_Seekers 12,654
-
add-command
Create new VS Code commands with all required boilerplate
gitkraken/vscode-gitlens 9,774
-
add-ai-provider
Add a new AI provider integration to GitLens
gitkraken/vscode-gitlens 9,774
-
add-icon
Add new icons to the GitLens GL Icons font
gitkraken/vscode-gitlens 9,774
-
add-webview
Create new webviews with IPC protocol, Lit app, and registration
gitkraken/vscode-gitlens 9,774
-
analyze
Deep design and implementation analysis with devil's advocate evaluation
gitkraken/vscode-gitlens 9,774
-
audit-commits
Audit commits for issues and CHANGELOG entries
gitkraken/vscode-gitlens 9,774
-
challenge-plan
Use when reviewing or stress-testing a proposed technical approach, implementation plan, or architecture decision. Triggers when asked to review a plan, play devil's advocate, poke holes, or validate an approach before implementation begins.
gitkraken/vscode-gitlens 9,774
-
commit
Create well-formatted git commits following GitLens conventions
gitkraken/vscode-gitlens 9,774
-
create-issue
Create GitHub issues from uncommitted changes or commits
gitkraken/vscode-gitlens 9,774
-
deep-planning
Use when formulating the best technical approach for a task — before writing implementation plans or code. Triggers on architecture decisions, complex features, refactors, or when the user asks how to approach something. Investigates current codebase, questions existing patterns, researches alternatives, and presents approaches with trade-offs.
gitkraken/vscode-gitlens 9,774
-
deep-review
Use when reviewing a change set before merge, when tracing code paths for correctness, or when a thorough merge-blocking review is needed rather than a surface-level checklist
gitkraken/vscode-gitlens 9,774
-
inspect-live
Launch VS Code with GitLens via Playwright and inspect the running extension — read UI text, check feature flags, read logs, take screenshots
gitkraken/vscode-gitlens 9,774
-
investigate
Structured investigation of a bug or unexpected behavior before implementing a fix
gitkraken/vscode-gitlens 9,774
-
review
Code review against GitLens standards with optional impact completeness audit
gitkraken/vscode-gitlens 9,774
-
worktree
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees following GitLens conventions
gitkraken/vscode-gitlens 9,774
-
add-test
Generate unit or E2E test files for existing code
gitkraken/vscode-gitlens 9,774
-
init
This skill should be used when a user asks to initialize a repository for AI agents, create or update an AGENTS.md file, scaffold agent instructions for a codebase, or improve existing agent guidance. Triggers include phrases like 'create an AGENTS.md', 'set up agent instructions', 'initialize this repo for coding agents', 'update my AGENTS file', or 'analyze this repo and generate agent docs'.
srtab/daiv 18
-
code-review
This skill should be used when a user asks for a code review, feedback on a PR or MR, diff assessment, or says things like 'can you review my changes', 'look at this diff', 'is this ready to merge', 'check my code', 'review this branch', 'what do you think of these changes', or 'LGTM check'. Covers correctness, tests, performance, security, and architecture feedback on pull/merge requests or raw diffs from any platform (GitHub, GitLab).
srtab/daiv 18