Results for “issue”

Debug issues by investigating logs, database state, and git history

Analyze Azure resources and IaC files to identify cost optimization opportunities, calculate savings, and create GitHub issues for tracking.

Manage GitLab issues, merge requests, CI/CD pipelines, and repositories from the terminal using the glab CLI, including support for self-hosted instances and automation scripts.

Performs GitHub operations from the terminal using the gh CLI, including auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management.

Manage GitHub repositories via the gh CLI: triage issues, review PRs, debug CI failures, create releases, and monitor security alerts.

GitHub 이슈 번호를 받아 본문·코멘트·첨부 이미지를 gh로 수집해 실제로 읽고, 프론트엔드/백엔드 성격에 맞춰 코드베이스와 대조 분석해 계획을 세운 뒤, 워크트리를 만들어 구현하고 커밋하고, 전후 증거를 webp 로 캡처해 기본 브랜치에 먼저 커밋한 다음 이슈에 렌더링되는 리포트를 남깁니다. 이슈 번호 대신 작업 설명을 주면 issue-create 로 이슈부터 등록합니다. `$issue-start`, "이슈 착수", "이슈 분석하고 작업해줘" 요청에 사용합니다.

Provides a framework for designing and implementing a company operating system, covering accountability charts, scorecards, meeting rhythms, issue resolution, and quarterly priorities.

Manage GitHub repositories: triage issues, review PRs, debug CI/CD, prepare releases, and monitor security alerts using the gh CLI.

Coordinates GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear tracks internal execution.

Use when reporting bugs, doing QA, or filing GitHub issues conversationally

Add a comment to a GitHub issue or pull request

Manages GitHub repositories via the gh CLI: triaging issues, reviewing PRs, debugging CI failures, preparing releases, and monitoring security alerts.

Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.

Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.

Interact with Gitea repositories, issues, pull requests, releases, and more via the gitea-mcp server or the tea CLI, with automatic detection of Gitea remotes.

Establish and verify exclusive ownership of a GitHub issue before refine, design, or implementation work begins. Use from ticket-mode workflows that must claim an unassigned issue for the active GitHub CLI user without replacing existing assignees.

Use when encountering blockers, unresolved issues, or problems beyond your authority or capability. This skill provides a structured escalation process ensuring issues are escalated to the right level with proper context, and tracked through resolution.

Prepare release notes, issue drafts, and GitHub release readiness checks.

Audit a component or page for accessibility issues and fix them

Guidelines for upgrading Expo SDK versions and fixing dependency issues

Audit a component or page for accessibility issues and fix them

Audit a component or page for accessibility issues and fix them

Use the GitHub CLI (gh) to perform core GitHub operations: auth status, repo create/clone/fork, issues, pull requests, releases, and basic repo management. Trigger for requests to use gh, manage GitHub repos, PRs, or issues from the CLI.

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Load this skill when the user says "plan milestone", "plan-milestone", or "/plan-milestone". Derives sub-issues for a milestone epic, persists all artifacts to disk, enforces UI enrichment via Stitch, and creates GitHub issues only after full approval.

Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.

Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.

Diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance.

Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer.

Escribe mensajes de commit, PRs e issues con tono humano en español rioplatense o técnico en inglés, siguiendo reglas de atomicidad, límite de 300 líneas y verificación previa de tests.

Git-native issue tracking with first-class dependency support. Issues stored alongside code in .beads/ directory, dual-persisted in SQLite (queries) and JSONL (git-friendly history). Hash-based IDs, DAG dependencies, daemon mode with RPC, and LSP-inspired multi-workspace support.

Drafts U.S. internal legal memoranda using IRAC structure to analyze issues, synthesize authority, assess risks, and recommend strategy. Use when asked to draft a research memo, internal memo, issue analysis, case strategy memo, or any IRAC-based legal analysis.

Break a work-items.md file (produced by /plan-work-items) into independently-grabbable GitHub issues, one per slice, in each slice's target repo. Use when you want to turn a work-items file into GitHub issues, publish work items as issue tickets, or create implementation tickets that can be worked on and tracked on GitHub. Does not produce the work-items file itself — use plan-work-items to break a plan into work items first. Does not review code or post pull request comments — use post-code-review-to-pr for that.

Code review is time-consuming and inconsistent. Reviewers miss security issues, overlook edge cases, or focus on style over substance. Meanwhile, AI agents catch these mechanical issues instantly but can't judge business logic correctness, UX decisions, or architectural fit.

Use the `gh` CLI for issues, pull requests, Actions runs, and GitHub API queries.

Prepare release readiness notes, version checks, test checklist, and local issue drafts.