Claude Skills by synesenom

You are running the full research-to-PR pipeline autonomously: `/research` → `/plan` → `/implement` → `/validate` → `/review` → ship.

You are creating a git commit for the current staged and unstaged changes with an AI-generated commit message.

You are documenting a solved problem so that future sessions can learn from it.

You are doing free-form exploration of a statistical or mathematical topic by combining web research with codebase analysis, documenting findings in a structured exploration note.

You are eliminating all code smells in a target file using CodeScene's Code Health analysis as your guide.

You are fixing a straightforward GitHub issue that does not require research or planning — just do the work and ship it.

You are applying a small, targeted fix without the full research/plan/implement pipeline.

You are executing an approved implementation plan step-by-step.

You are picking the most appropriate next issue to work on from the open GitHub backlog.

You are creating a detailed implementation plan based on research findings.

You are creating a GitHub Pull Request for the current branch with an AI-generated summary that highlights non-trivial changes for manual review.

You are pushing local commits to the remote repository.

You are cutting a versioned release of ranjs: bumping the version, updating the changelog, creating and merging a release PR, and handing off to the GitHub Actions release workflow which tags, publishes to npm, cuts the GitHub release, and rotates the milestone. This skill runs **entirely through GitHub MCP tools** — it needs neither the `gh` CLI nor a local git tag push. Everything the skill cannot do from an MCP-only environment (create the `v*` tag, `npm publish`, cut the GitHub release, r...

You are conducting comprehensive codebase research to document what exists without suggesting changes.

You are triaging a GitHub issue to pick and launch the fastest, safest workflow: `/hotfix`, `/fix`, or `/build`.

> **Scope:** This skill is for reviewing **externally submitted GitHub PRs** (pull requests opened by contributors on GitHub). It is entirely distinct from: > - `/review` — reviews *local* branch changes before committing; used inside the `/build` pipeline > - `review-security`, `review-correctness`, etc. — internal quality-check subagents spawned by `/review` and `/build`; never invoked by users directly > > Do **not** use this skill during task resolution. It is only for triaging incoming c...

You are performing a pre-commit code review of the current branch's changes against `main`.

You are generating and triaging potential future issues by scanning the codebase through specialist agents, deduplicating against existing issues, and letting the user pick which to create.

You are validating that a GitHub issue's problem has been fully resolved by the current branch's implementation.