メニュー
Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement advanced Symfony 8.1 components: async/queues with Messenger (#[AsMessageHandler], transports, retry, failed messages), Serializer (serialize/deserialize, groups, context), Workflow & state machines (places/transitions, guards, transition listeners), Mercure realtime updates, Lock (mutexes/critical sections), HTTP Client (HttpClientInterface), Cache pools (CacheInterface, tags), Rate Limiter (RateLimiterFactoryInterface), Scheduler (#[AsSchedule], RecurringMessage), and Webhook/RemoteEvent consumers. Use whenever a task mentions queues, background jobs, async processing, message bus, serialization to JSON, state machines, realtime/SSE, distributed locks, calling external APIs, caching, throttling/rate limiting, cron/recurring tasks, or incoming webhooks.
Use for ANY Symfony AI task: integrating LLMs/AI into a Symfony or PHP app via the Symfony AI components. Covers the Platform component (unified interface to OpenAI, Anthropic Claude, Google Gemini, Azure, Mistral, Ollama), building an AI Agent, tool calling with the #[AsTool] attribute, Retrieval Augmented Generation (RAG) with a vector Store and embeddings, the Chat component and conversation memory, configuring everything through the AI Bundle YAML (config/packages/ai.yaml), and exposing or consuming an MCP server (MCP Bundle / Mate). Trigger on symfony/ai, ai-bundle, AsTool, MessageBag, vectorizer, SimilaritySearch, McpTool, or any "add AI/chatbot/embeddings/RAG to Symfony".
Build and wire the core architecture of a Symfony 8.1 app. Use this whenever you work with the service container, dependency injection, autowiring, service tags, factories, service decoration, the event dispatcher (listeners/subscribers), bundles, the kernel, or app configuration (config/packages, environment variables, secrets, parameters). Reach for this skill before creating a service class, injecting a dependency, hooking into a kernel event, or editing config.
Use when building Symfony 8.1 web pages and features: creating routes, controllers, Twig templates, Doctrine entities and CRUD, forms, and validation. Reach for this skill whenever you create a page, wire a URL to a controller, render HTML with Twig, persist or query data with Doctrine entities/repositories, build a Symfony form, or add validation constraints.
Use for Symfony 8.1 deployment, production configuration, and operations. Covers deploying (APP_ENV=prod, composer install --no-dev --optimize-autoloader, cache:clear/warmup, dump-env), performance tuning (OPcache, realpath cache, preloading, container single-file, classmap-authoritative), HTTP caching (Cache-Control, Expires, ETag, Last-Modified, Vary, reverse proxy, invalidation/PURGE), profiler and debugging, logging with Monolog (handlers, channels, fingers_crossed), testing with PHPUnit (WebTestCase, KernelTestCase, assertions, database), and Symfony best practices. Trigger whenever a task mentions deploy, prod env, opcache, performance, HTTP cache, reverse proxy, profiler, Monolog/logs, PHPUnit tests, or production hardening of a Symfony app.
Use for ALL Symfony 8.1 security work: authentication and authorization, login (form_login, json_login, http_basic, login link), firewalls and security.yaml, user providers, roles and role_hierarchy, password hashing, access control (access_control, #[IsGranted], denyAccessUnlessGranted), voters, CSRF protection, logout, and custom authenticators. Trigger whenever a task mentions login, secure a route, protect an endpoint, roles, permissions, hashing passwords, who can access, firewall, or security.yaml.
| name | github |
| description | Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries. |
| risk | safe |
| source | Dimillian/Skills (MIT) |
| date_added | 2026-03-25 |
Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.
gh issue, gh pr, gh run, or gh api from the command line.Check CI status on a PR:
gh pr checks 55 --repo owner/repo
List recent workflow runs:
gh run list --repo owner/repo --limit 10
View a run and see which steps failed:
gh run view <run-id> --repo owner/repo
View logs for failed steps only:
gh run view <run-id> --repo owner/repo --log-failed
Follow this sequence to investigate a failing CI run:
gh pr checks 55 --repo owner/repo
gh run list --repo owner/repo --limit 10
gh run view <run-id> --repo owner/repo
gh run view <run-id> --repo owner/repo --log-failed
The gh api command is useful for accessing data not available through other subcommands.
Get PR with specific fields:
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'
Most commands support --json for structured output. You can use --jq to filter:
gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'