suzuki-shunsuke

Choose and configure where ghtkn stores access tokens (keyring, text, agent). Use when the OS keyring is unavailable (containers, microVMs), or when setting up the ghtkn agent backend.

Configure ghtkn via config file, environment variables, and CLI args. Use for configuration priority, disabling browser open, the GitHub account picker, enterprise GitHub App sharing, or GHTKN_GITHUB_TOKEN.

Understand how ghtkn works internally and how its tokens compare to alternatives. Use to explain the token workflow, compare with GitHub CLI OAuth / fine-grained PAT / installation tokens, or discuss API rate limits.

Configure ghtkn as a Git credential helper and switch GitHub Apps by repository owner. Use when setting up git authentication via ghtkn, handling fork repos, or troubleshooting the credential helper on macOS.

Install the ghtkn CLI and verify downloaded release assets. Use when installing ghtkn via Homebrew, Scoop, aqua, go install, or GitHub Releases, or verifying assets with gh / slsa-verifier / Cosign.

Configure and switch between multiple GitHub Apps in ghtkn. Use when setting up per-organization apps, selecting an app by argument or GHTKN_APP, or switching apps per directory with direnv.

Revoke leaked or compromised ghtkn access tokens. Use during incident response, when a token leaks, or to revoke an app's stored token via ghtkn revoke or the GitHub REST API.

Manage the ghtkn access token lifecycle - regeneration, ghtkn auth, the automatic device flow, and clipboard. Use when tokens expire, configuring -min-expiration, authenticating, or copying the one-time code.

Creates agent skills from an OSS project's documentation. Splits the documentation other than README.md into per-topic skills/<oss>-<topic>/*.md files, and has README.md and SKILL.md reference them, so human-facing documentation and skills share the same body and avoid double maintenance. Use when turning an OSS project's documentation into skills, or restructuring existing documentation into a skill-based layout.

Writes commit messages following Conventional Commits in English. Use when the user asks to write, format, or improve a commit message.

Translates the document or text in context into English. Use when the user asks to translate something into English, or invokes /en.

Conventions and commands for Go projects — testing, linting, JSON Schema generation, and error handling. Use when developing, testing, or linting Go code in this repository.

Baseline rules for this repository — use English, never commit to default branches, never rewrite commit history. Use at the start of any coding or git task.

Creates a branch, commits the changes, and opens a pull request whose description summarizes the full diff between base and head. Use when the user asks to create a pull request, open a PR, or submit changes for review.

Reviews an agent skill's SKILL.md against authoring best practices and reports findings by severity. Use when the user asks to review, audit, or check the quality of an agent skill or a SKILL.md.

Use this skill when working with validate-pr-review-app, a self-hosted GitHub App that validates Pull Request reviews to ensure PRs cannot be merged without proper approvals. Use this skill when the user wants to: - Update the configuration of validate-pr-review-app (e.g. make an app trusted, add untrusted_machine_users, change approval requirements) - Understand why a PR requires two approvals or how to avoid the two-approval requirement - Troubleshoot PR merge failures related to approval validation Even if the user doesn't mention "validate-pr-review-app" by name — if they ask about PR approval requirements, trusted apps, or merge validation, this skill applies.