Development

Create, improve, or audit a GitHub project's README and open-source community-health files (LICENSE, CONTRIBUTING.md, CODE_OF_CONDUCT.md, issue/PR templates). Use when the user asks for a README, README quality/readability/accuracy/examples, or wants a repo's "open source credentials" / community-standards readiness checked. Do not use for full docs sites, API-reference-only work, or general code review.

Look up GitHub activity for people in a GitHub org by display name or handle. Summarizes PRs opened/merged/reviewed, repos touched, and provides a narrative of what each person worked on over a specified timeframe. Use when asked what teammates have been working on, for sprint reviews, team status reports, or manager 1:1 prep.

Systematically address all open GitHub PR review comments — fix code or decline with reasoning, reply to every thread, resolve when done

Merge Worktree to Main

Identify Unmerged Changes

Manage git worktrees for isolated feature development. Automatically handles directory selection, .gitignore safety verification, worktree creation, project setup (npm/cargo/poetry/go), and test baseline validation. Use when starting new feature branches, working on multiple features simultaneously, or needing clean isolated environments. Integrates with CLAUDE.md directives and handles common failure modes.

Use this skill when breaking a large change into a stack of reviewable PRs

Validate directional claims, walk times, and pedestrian routes using OSM data (Nominatim geocoding + Overpass queries). Fixes hallucinations about east/west/north/south, crossing barriers, and travel times by grounding everything in real coordinates.

Answer a question about a video game and synthesize the answer plus related mechanics into atomic Logseq wiki pages. Use when the user asks a game-mechanics/lore/item/how-to question about a game they're playing and wants both a direct answer and their personal wiki updated — e.g. "what does X do in No Man's Sky", "how do I get Y", or explicit phrasing like "synthesize this game info to my wiki."

Diagnose and fix CI failures on main or release branches. Checks GitHub Actions run status, reads failure logs, applies fixes, and verifies a re-run passes. Use when CI is red on main, a release is broken, or you want to confirm all checks are green before shipping.

Firebase + Firestore best practices for Kotlin Multiplatform (KMP) apps,

Analyze current changes and update any related outdated documentation

Apply design patterns from Gang of Four (GoF) and Patterns of Enterprise Application Architecture (Fowler/PoEAA). Use when structuring new code, evaluating design decisions, or identifying the right pattern for a problem. Covers when to use, when to avoid, and Go-idiomatic implementations.

Use this skill when Tyler asks to change a specific design parameter, fix a compliance FAIL item, move the island, adjust bar seating clearance, or apply a named change to design_spec.py. Requires a specific change target (field name or FAIL item from a review). DO NOT invoke for a general compliance review (use design:review) or the full iterative loop (use design:loop).

Check a design doc's markdown for constructs that render wrong, drop silently, or need a manual fixup when the doc is published/synced to its actual target (Confluence via markdown-confluence, or Google Docs/Confluence via docspan) — verified by lookup against that tool's current documented behavior, not guessed. One check in the design-doc-review pipeline — run standalone or via design-doc-review:review.

Write Confluence-compatible markdown for publishing via markdown-confluence tool. Covers syntax, frontmatter, directory structure, and Confluence-specific features.

Parallelization Examples and Patterns

Systematically implement a new feature following research-backed best practices from the Six-Phase Software Implementation Methodology, with intelligent parallelization and multi-agent coordination

Apply Spring Boot and Java coding standards when writing, reviewing, or designing Java code. Use for Spring Boot project structure, DDD patterns (Entities, Aggregates, Repositories, Domain Services), Clean Code principles in Java, PoEAA patterns (Repository, Data Mapper, Service Layer, Unit of Work), testing with JUnit 5 and Mockito, and Spring-specific best practices. Covers constructor injection, transaction boundaries, layer responsibilities, and common anti-patterns to avoid.

Execute Arlo Belshee's Core 6 Refactorings mechanically using available CLI tools across TypeScript, Go, Rust, and Java. Evaluates tool availability, routes to the most precise tool, and produces a reviewable git diff. Use for: rename symbol, extract function, inline variable, introduce variable, change signature, move symbol. Never hand-edits at scale. Covers: rename, extract, inline, introduce-variable, change-signature, move. Triggers on: Core 6, Belshee, mechanical refactor, rename method...

Trigger when the user asks to reverse engineer a closed-source Qt5/C++ Windows PE binary on Linux, recover Qt meta-objects (classes, signals, slots), trace Win32 API calls via Wine relay or WineDbg, hook network send/recv with Frida, capture and parse proprietary binary protocols (Wireshark → ImHex → Kaitai Struct), or analyze unknown binary file formats from embedded hardware. Also triggers for: "what does RayStudio send over the network", "recover class names from this DLL", "decode this sc...

Trace static call paths through a codebase — forward ("what does this entry point reach") and backward ("what reaches this function") — for impact analysis before a change, blast-radius estimation for an incident, dead-code detection, or verifying a security-relevant path (auth check, sanitizer) actually sits on every route to a sink. Language-agnostic: prefers LSP-based call hierarchy (serena MCP) when available, falls back to per-language call-graph tools, falls back further to an ast-grep/...

Idiomatic review for Kotlin Multiplatform (KMP) with Kotlin 2.x — expect/actual discipline, Swift boundary safety, ViewModel lifecycle, SQLDelight conventions

Discover Java API signatures from compiled JARs using javap instead of guessing or relying on incomplete documentation. Use when encountering unknown methods, pagination patterns, union types, or compilation errors from incorrect API assumptions.