github-graphql-api
GitHub REST APIのSub-issue関連バグを回避するためのGraphQL API共通処理(Sub-issue登録、エラーハンドリング)を提供
Essential command-line tools and system utilities.
GitHub REST APIのSub-issue関連バグを回避するためのGraphQL API共通処理(Sub-issue登録、エラーハンドリング)を提供
Enforces the standard development workflow for the fund-portfolio-bot project: read docs first, propose a small scoped design, respect version scope, and limit code changes. Use when implementing, modifying, or refactoring functionality in this repository.
This skill should be used when the user asks to "update docs", "sync documentation", "docs are outdated", "refresh README", or wants to update existing documentation to match current code. Spawns @writer agent to compare docs against codebase and update.
Repository of institutional memory, architectural standards, and security protocols for the indiiOS project. Defines the 'Laws' of the codebase.
Enforce structured git workflow with conventional commits, feature branches, semver versioning, and work logging. Use for all code changes to prevent work loss and maintain history.
Automatically runs project validation commands (linters, type checkers, tests) after file edits and blocks commits on any failure. Reads validation commands from CLAUDE.md or auto-detects from project type. Enforces strict quality gates to catch issues early. (project)
Explore codebase, understand architecture, find how things work. Navigate unfamiliar repositories, discover code structure, find where functionality lives by intent rather than exact text. NOT for debugging failures (use debugging) or checking change impact (use change-planning).
Suggest commit messages based on staged changes and assist with committing using an editor.
Manage git operations for spec-driven development. Use when creating branches for specs/features, generating commits, or creating PRs. Provides consistent git workflow across specify, implement, and refactor commands. Handles branch naming, commit messages, and PR descriptions based on spec context.
Audit codebase stability guardrails - tests, ESLint, pre-commit hooks, CI/CD, dead code detection with Knip. Finds unused files, exports, and dependencies. Use /codebase-stability-audit:run to start.
Generate commitlint configuration files for enforcing conventional commit messages. Triggers on "create commitlint config", "generate commit lint", "commitlint setup", "commit message rules".
Visualize proposed code changes in a structured ASCII format with file tree, impact summary, syntax-highlighted diff, and rationale. Use this skill when proposing refactors, simplifications, or any code modifications.
Generate comprehensive documentation for codebases, suitable for both human developers and AI coding assistants. Use when documenting a repository, creating architecture docs, generating API references, writing onboarding guides, or creating CLAUDE.md/AGENTS.md files for AI assistants working with the codebase.
This skill should be used when the user asks to "review code with codex", "run codex review", "check code quality", "codex レビュー", mentions "レビューゲート", or before git commit/PR/merge/release. Performs iterative code review using read-only Codex CLI, with Claude Code making fixes until ok:true is achieved. Use after spec/PRD/requirements creation, major steps (>=5 files/new modules/public APIs/infra changes), and before git operations.
Scan project folder structure, validate organization, clone GitHub repository, and generate an inventory of available materials. First step of writer workflow. Use when starting a new manuscript project.
Examines git diffs between commits or branches with intelligent analysis. Provides unified diff format with comprehensive summaries including file statistics, rename detection, and merge commit handling. Outputs formatted diffs to /claudedocs for documentation and review purposes.
Use when user says 'gh project create', 'GitHub Project 作成', 'プロジェクト作成', 'create project', or discusses creating a new GitHub Project. Ensures projects have proper short description and README.
Guidance for structuring and organizing justfiles. Use when creating, editing, or discussing justfile organization, command grouping, or repo CLI conventions.
Create and execute git commit plans from YAML files - use when organizing changes into logical commits or when user wants help structuring their git history
PROACTIVELY USE after implementing code to add docstrings, type hints, cleanup. Delegates grunt work to local LLMs — saves cloud tokens. Files must be <500 lines. Use for mechanical polish, not logic changes. Changes are auto-applied.