codex-review
Codex CLI(read-only)を用いて、レビュー→Claude Code修正→再レビュー(ok: true まで)を反復し収束させるレビューゲート。仕様書/SPEC/PRD/要件定義/設計、実装計画(PLANS.md等)の作成・更新直後、major step(>=5 files...
Discover development automation tools skills, compare source repositories and read the instructions for each workflow.
Codex CLI(read-only)を用いて、レビュー→Claude Code修正→再レビュー(ok: true まで)を反復し収束させるレビューゲート。仕様書/SPEC/PRD/要件定義/設計、実装計画(PLANS.md等)の作成・更新直後、major step(>=5 files...
Creates, analyzes, updates, and improves slash commands including YAML frontmatter, argument handling, and command authoring workflows. Use when user asks how slash commands work, explaining command syntax and...
Creates, packs, bundles, and manages Claude Code plugins with manifest generation, directory structure, marketplace configuration. Use when user asks how plugins work, what plugins are, explaining plugin struct...
Creates, analyzes, updates, and improves Claude Code hooks including configuration, scripts, and security validation. Use when user asks how hooks work, explaining hook concepts, understanding hook types and ev...
Creates, updates, and maintains CHANGELOG.md files following Common Changelog and Keep a Changelog standards. Use when creating changelogs, adding release entries, updating unreleased sections, validating chang...
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
gh CLI の高度な使い方、使用頻度の低いサブコマンド、便利なオプションを提供。trigger「gh の使い方」「GitHub API を叩きたい」「gh」「use gh」
Codex CLIでレビュー・分析をする。「codexにレビューして」「レビューして」「review my changes」と依頼された際に使用
This skill shoudl be used when the user ask to "behaviors", "specification", "read implementation", "analyze component", "振る舞いを分析", "振る舞いを理解". Analyze component(module, package, class, function) b...
Security best practices and guidelines for the Jarvy CLI codebase - a cross-platform development environment provisioning tool that executes system commands with elevated privileges
Code quality guidelines for Jarvy CLI - Rust formatting, Clippy linting, error handling patterns, documentation standards, and Conventional Commits.
Analyze code changes and recommend appropriate documentation. Evaluates git diffs to determine if changes warrant README updates, inline doc additions, or dedicated documentation files. Triggers on: document ch...
Dependency management guidelines for Jarvy - crate selection criteria, feature flag best practices, version management, security auditing with cargo-audit and cargo-deny.
Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.
Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.
Use to review code implementations for quality, correctness, and best practices
Use after completing user-visible features, fixes, or behavior changes - NOT for internal docs (CLAUDE.md, DECISIONS.md, _tasks/)
Codebase-specific context for AI agents using Upstash Redis. Indexes documentation and provides relevant context for queries. Perfect for Q&A about codebases.
Manage unpublished content in Quartz static site repos. Use when: (1) User wants to prevent files without `publish: true` from being committed (2) User asks about gitignoring based on frontmatter content (3) Us...
Skill for committing changes to this repository using Git, generating a commit message from recent history and current changes.
Use when releasing a new version, updating CHANGELOG.md, or user asks to document changes - enforces Keep a Changelog format with proper categorization derived from conventional commits
Quick CI/CD failure diagnosis. Use when builds fail.
Diagnose CI/CD pipeline failures, analyze Jenkins build logs, and troubleshoot deployment issues. Use when builds fail, checking pipeline status, investigating errors, or understanding deployment health.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.