Git & VCS
Git operations, commit helpers, branch management
railway-docs
by railwayapp
This skill should be used when the user asks about Railway features, how Railway works, or shares a docs.railway.com URL. Fetches up-to-date Railway docs to answer accurately.
crafting-readme-files
by Dicklesworthstone
Craft professional README.md files for GitHub open source projects. Generates hero sections, installation instructions, feature tables, and architecture diagrams. Use when creating or revising a README, documenting a CLI tool, library, or open source project, or when user asks about README structure, badges, or project documentation.
ci-cd-pipelines
by rohitg00
CI/CD pipeline patterns for GitHub Actions, GitLab CI, testing strategies, and deployment automation
history-analyzer
by lis186
Analyze git history for hotspots, coupling, and knowledge distribution. Use when user asks "who knows this code", "what files change most", "hotspots", "bus factor", "knowledge silos", or needs to understand code evolution.
history
by lis186
Smart temporal analysis using git history - Hotspots, Coupling, and Recent Contributors
issue-auto-sync
by jmagly
MCP tools: Gitea issue management
swarm
by boshu2
'Spawn isolated agents for parallel task execution. Local mode auto-selects runtime-native teams (Claude Native Teams in Claude sessions, Codex sub-agents in Codex sessions). Distributed mode uses tmux + Agent Mail (process isolation, persistence). Triggers: "swarm", "spawn agents", "parallel work", "run in parallel", "parallel execution".'
pr-prep
by boshu2
'PR preparation: git archaeology, test validation, structured PR body generation. Mandatory user review gate before submission. Triggers: "prepare PR", "PR prep", "submit PR", "create PR body", "write PR description".'
pr-implement
by boshu2
'Fork-based PR implementation with isolation check. Runs isolation check before starting work. Triggers: "implement PR", "implement contribution", "fork implementation", "code the PR".'
pr-validate
by boshu2
'PR-specific validation: isolation, upstream alignment, quality, scope creep. Triggers: "validate PR", "pr validation", "check PR scope", "scope creep check", "isolation check".'
reverse-engineer-rpi
by boshu2
'Reverse-engineer a product into a feature catalog, code map, and specs. Uses RPI-style loop with verification gates. Triggers: “reverse engineer”, “catalog features”, “feature inventory”, “code map”, “docs to code mapping”, “binary analysis”.'
quickstart
by boshu2
'Interactive onboarding for new users. Guided RPI cycle on your actual codebase in under 10 minutes. Triggers: "quickstart", "get started", "onboarding", "how do I start".'
trace
by boshu2
'Trace design decisions and concepts through session history, handoffs, and git. Triggers: "trace decision", "how did we decide", "where did this come from", "design provenance", "decision history".'
security
by boshu2
'Continuous repository security scanning and release gating. Triggers: "security scan", "security audit", "pre-release security", "run scanners", "check vulnerabilities".'
pr-research
by boshu2
'Upstream codebase exploration for open source contribution. Outputs contribution guidelines, PR patterns, and maintainer expectations. Triggers: "pr research", "upstream research", "contribution research", "explore upstream repo".'
bug-hunt
by boshu2
'Investigate suspected bugs with git archaeology and root cause analysis. Triggers: "bug", "broken", "doesn''t work", "failing", "investigate bug", "debug", "find the bug", "troubleshoot".'
release
by boshu2
'Release your software. Pre-flight validation, changelog generation, version bumps, release commit, tag, curated release notes. Boundary: everything up to the git tag. Triggers: "release", "cut a release", "prepare release", "release check".'
beads
by boshu2
'This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what''s ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.'
amiberry-jit-fix
by BlitterStudio
ARM64 JIT compiler fixes for Amiberry (GitHub issue #1766). This skill captures the complete technical knowledge from 20+ debugging sessions that identified and fixed: (a) a page 0 DMA corruption crash during A1200 Kickstart boot, (b) visual corruption (black gadgets, garbled text) caused by incorrect inter-block flag optimization, (c) SIGSEGV crashes on unmapped natmem gaps (e.g., 0x00F10000) in complex configs with hardfiles/RTG, and (d) BSR.L/Bcc.L backward branch crashes from 32-bit displacement zero-extension on 64-bit platforms. Use this skill when working on: (1) the JIT_DEBUG_MEM_CORRUPTION code in compemu_support_arm.cpp or newcpu.cpp, (2) the page 0 DMA guard mechanism (mprotect/SIGSEGV/BRK single-step), (3) any ARM64 JIT register width bugs (64-bit vs 32-bit instruction selection), (4) any crash or exception cascade during A1200 boot with JIT enabled, (5) 68040 JIT mode issues on ARM64, (6) the inter-block flag optimization bug and its fix (dont_care_flags at block boundaries), (7) natmem gap crashes and the commit_natmem_gaps() fix in amiberry_mem.cpp. MANDATORY TRIGGERS: JIT crash, page 0, DMA guard, vec2, exception vector corruption, blitter DMA, mprotect, SIGSEGV handler, BRK single-step, ARM64 JIT, Kickstart boot, visual corruption, black gadgets, garbled ROM version, compemu_support_arm, JIT_DEBUG_MEM_CORRUPTION, inter-block flag, dont_care_flags, 68040 JIT, natmem gap, unmapped region, commit_natmem_gaps, 0x00F10000, canbang, PROT_NONE, BSR, Bcc, branch displacement, sign extension, comp_pc_p, comp_get_ilong, 64-bit pointer, zero-extend, backward branch, gencomp_arm.
requesthunt
by ReScienceLab
Generate user demand research reports from real user feedback. Scrape and analyze feature requests, complaints, and questions from Reddit, X, and GitHub. Use when user wants to do demand research, find feature requests, analyze user demand, or run RequestHunt queries.
llvm-learning
by gmh5225
Comprehensive learning resources and tutorials for LLVM, Clang, and compiler development. Use this skill when helping users learn LLVM internals, find educational resources, or understand compiler concepts.
noir-frontend-tests
by noir-lang
Guide for writing noirc_frontend unit tests. Use when adding, writing, or reviewing frontend tests — regression tests, reproduction tests, error-checking tests, or should_panic tests in the compiler frontend.
sequential-thinking
by majiayu000
"Structured reflective problem-solving methodology. Process: decompose, analyze, hypothesize, verify, revise. Capabilities: complex problem decomposition, adaptive planning, course correction, hypothesis verification, multi-step analysis. Actions: decompose, analyze, plan, revise, verify solutions step-by-step. Keywords: sequential thinking, problem decomposition, multi-step analysis, hypothesis verification, adaptive planning, course correction, reflective thinking, step-by-step, thought sequence, dynamic adjustment, unclear scope, complex problem, structured analysis. Use when: decomposing complex problems, planning with revision capability, analyzing unclear scope, verifying hypotheses, needing course correction, solving multi-step problems."
vue-jsx-best-practices
by vuejs-ai
JSX syntax in Vue (e.g., class vs className, JSX plugin config).