Results for “issue”

Diagnose and resolve Debian Linux issues using apt, systemd, and AppArmor-aware guidance.

Runs ESLint to review code for style and correctness issues, with setup and documentation references.

Safely create, adopt, publish, or clean up an issue-backed non-primary Git branch without force-pushing or absorbing ambiguous work

When reviewing code, generate the complete corrected version — not just the issues, but the exact fixed code ready to copy-paste.

Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. (gstack)

Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.

Triggers a code-review subagent after tasks, features, or before merging to catch issues early.

Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose

Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose

Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose

Diagnose and resolve Arch Linux issues using pacman, systemd, and rolling-release best practices.

Create pull requests following Sentry's engineering practices, including drafting descriptions, titles, and issue references.

Datadog CLI for searching logs, querying metrics, tracing requests, and managing dashboards. Use this when debugging production issues or working with Datadog observability.

Dispatch a code reviewer subagent to catch issues before they cascade, with precisely crafted context for evaluation.

Upgrade Expo SDK versions and fix dependency issues with step-by-step guidance.

Debug application issues with techniques for Python, JavaScript, performance profiling, production incidents, and network problems.

Turns working-tree changes into well-formed local commits following Conventional Commits, with atomic boundaries and issue references.

Turn a resolved support issue into a search-friendly, self-service knowledge-base article that deflects future tickets — with internal notes kept separate.

AL performance optimization patterns for Business Central. Use when optimizing queries with SetLoadFields, working with FlowFields and CalcFields, profiling codeunits, or resolving performance issues.

Run PRINCE2 Controlling a Stage: work package tracking, highlight reports, risk and issue control, tolerance checks, change handling, and corrective action planning.

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Finds, analyzes, and strategizes for high-impact open source contribution opportunities in trending repositories.

Diagnose and resolve CentOS Linux issues with RHEL-compatible commands, SELinux-aware practices, and firewalld considerations.

Interact with GitLab via helper functions for merge requests, issues, pipelines, and code review comments.

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Performance-coaching mode for repeated failures, passive behavior, completion-quality issues, or explicit try-harder requests. Uses structured troubleshooting and evidence-first delivery habits.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue re...

Structured policy briefing note (1-2 pages). Issue, background, analysis, options, recommendation. UK GES, Australian Treasury, consulting formats. Auto-populates from econstack data skills.

Interact with GitHub issues, pull requests, Actions runs, and the GitHub API using the `gh` CLI.

Remove assigned mypy exclusion modules in small batches, fix typing issues, run validation, and produce a structured completion summary.

Diagnoses Qdrant production issues using metrics and observability tools, covering optimizer problems, memory spikes, and slow queries.

Reviews code changes with a second AI reviewer, validates reported issues against the actual code, and reports only confirmed findings.

Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.