tokyo-geek

Audit a blog post for content quality - verify facts are correct and up-to-date, check style-guide compliance, and confirm the content is logically sound and complete. Produces a structured audit report grouped by accuracy, style, and sense, with severity, location, and a recommended fix for each finding. Use when a user asks to audit, fact-check, review, or quality-check a content Markdown file under contents/.

Polish one or more Markdown files so the repo core writing rules are enforced - straight quotes (not curly), no contractions, the Oxford comma, sentence case headings, plain hyphens (never en-dash or em-dash), consistent capitalization and punctuation, simple non-idiomatic wording, no sentence split across a line break, and no slash standing in for "or" or "and". After applying these fixes, also runs the link-polisher skill on the same files to format raw URLs. Use when a user asks to polish, clean up, style-check, or enforce writing rules on a Markdown file, or before committing prose changes to docs.

Lint and polish Markdown files in this repo - run the repo auto-fixers, refresh any table of contents, convert inline and autolink links to reference-style links per the repo Markdown style guide, and check style-guide compliance. Use when a user asks to lint, clean up, or style-check a specific Markdown file, or all the Markdown files under contents/.

Translate a paired content Markdown file between English and Japanese to keep the two language versions in sync. Detects direction (EN->JA or JA->EN) from the source path, finds the 1-to-1 counterpart under the other language folder, translates the prose while preserving frontmatter structure, Markdown, code, links, and VitePress directives, applies the target-language style guides and the EN-JA glossary, and reconciles the `localization` frontmatter state. Use when a user asks to translate, localize, sync, or update the other-language version of a content file, or after editing a `sync` file whose counterpart is now `TODO: drifted`.

Auto-gather git changes, confirm scope with the user, and draft a commit title and message following the project commit style guide.

Lint repository file and folder names for format compliance. Use when users ask to check naming conventions, enforce file extensions, or validate notes naming patterns; applies a fixed set of rules from the skill and reports any discovered repository style guides for reviewer reference.

Audit the repository for missing or outdated folder `README.md` files. Use after adding new folders, moving files between folders, renaming files, or whenever folder contents change in a way that may make existing READMEs inaccurate.

Interact with GitHub repositories using the GitHub CLI (gh). Covers pull requests, issues, releases, workflow runs, and branch operations. Supports beginner and intermediate tracks, write-operation confirmation, and an --auto flag to skip prompts.

Generate a `tasks/<n>-<slug>.md` scaffold from a GitHub issue. Fetches the issue via `gh`, extracts linked spec issues and Figma URLs, infers the Phrase project, tag, and branch, and writes a minimal task file matching the existing `tasks/` style. Pass `--enrich` to also pull the body of every linked spec issue into a Spec details section. Accepts an issue number, `owner/repo#n`, or a github.com issue URL.

Fetch all comments on a GitHub pull request (reviews, inline review comments, and general issue comments) and emit a single consolidated Markdown report. Use when a user wants to read, summarize, audit, or triage every comment on a PR in one place. Accepts a PR number, a `owner/repo#n` reference, or a github.com pull-request URL.

Rewrite raw, unformatted URLs in Markdown files as Markdown links with a sensible human-readable label fetched from the source (Figma file name, GitHub issue or pull request title, etc.). A raw URL is any link that is not already wrapped in Markdown link syntax `[text](url)` with a meaningful label - this includes bare URLs, angle-bracketed autolinks (`<https://...>`), and links whose visible text is the URL itself or a generic placeholder like `Figma` or `github.com`. Use when a user adds or pastes a raw URL, asks to polish or format links, or when you notice an existing bare link in a Markdown file you are editing or reviewing. Currently supported link types: Figma (`figma.com`), and GitHub issues and pull requests (`github.com/<owner>/<repo>/issues/<n>` or `/pull/<n>`). Other URLs are kept as-is unless the user explicitly asks to polish them.

Audit the repository for missing or outdated folder `README.md` files. Use after adding new folders, moving files between folders, renaming files, or whenever folder contents change in a way that may make existing READMEs inaccurate.

Audit and enforce the AGENTS.md "Scripts" guidelines for helper scripts in this repo - banning Python, preferring Node.js `.mjs` modules or zsh, requiring `--help` output, a top-of-file notes section (general notes, usage, output), and status emojis. Use when adding or reviewing a helper script, or to sweep the repo for scripts that do not follow the guidelines.

Fully sync `Skill(<name>)` entries in `.claude/settings.json` under `permissions.allow` with the skills in the repo's `skills/` folder, adding entries for new skills and removing entries for skills that no longer exist.