List open issues in a GitHub repo

List all currently open issues in the repository "acme-corp/web-platform".
Display the issue number, title, and assignee for each.

Fix login redirect loop

Add dark mode support

Update README with API docs

Memory leak in websocket handler

Migrate to Node 20

gh issue list.*--repo acme-corp/web-platform.*--state open


Create a GitHub issue with title and body

Create a new issue in the repository "acme-corp/web-platform" with the title
"Add rate limiting to public API endpoints" and a body that describes the need
to prevent abuse on unauthenticated API routes.

Existing issue

gh issue create.*--repo acme-corp/web-platform.*--title


List channels in Slack workspace

List all public channels in the Slack workspace. Show the channel name,
member count, and topic for each channel.


Send a message to a Slack channel

Send the message "Deployment v2.3.1 completed successfully. All health checks passing."
to the #engineering channel in Slack.


List issues assigned to a specific user in Linear

List all issues in Linear that are currently assigned to the user "sarah@acme.com".
Show the issue identifier, title, status, and priority.

Implement OAuth2 PKCE flow

Database migration script

Update CI pipeline

Add Sentry error tracking

Refactor user service


Create a Linear issue with priority

Create a new issue in the Linear team "Platform" with the title
"Implement webhook retry logic with exponential backoff", set the priority
to "urgent", and assign it to "sarah@acme.com".

Existing backlog item


Search for Slack messages containing a keyword

Search the Slack workspace for all messages containing the keyword "outage"
from the last 7 days. Display the channel, sender, timestamp, and message text.

incidents

ALERT: Database outage detected in us-east-1

Investigating the outage — looks like connection pool exhaustion

Restarting the affected pods now

engineering

FYI the outage yesterday was caused by a bad migration

PR #234 is ready for review


View a specific GitHub issue by number

View the full details of issue #42 in the repository "acme-corp/web-platform",
including its title, body, labels, assignee, and comments.

Fix login redirect loop

Users are experiencing an infinite redirect loop when logging in
with SSO. The issue occurs after the OAuth callback redirects back
to the application. Browser console shows ERR_TOO_MANY_REDIRECTS.

I can reproduce this on Chrome 120 with SSO provider Okta.

Found the root cause — the session cookie domain is misconfigured.

gh issue view 42.*--repo acme-corp/web-platform


List projects in Linear

List all projects in the Linear workspace. Show the project name, status,
lead, and target date for each project.

Q1 Platform Migration
Mobile App v3
Security Audit Remediation
Design System 2.0


Send a DM to a user on Slack

Send a direct message to the Slack user "alice" with the text:
"Hey Alice, can you review PR #234 when you get a chance? It's the auth fix we discussed."


Add a label to a GitHub issue

Add the label "priority:high" to issue #45 in the repository
"acme-corp/web-platform". The issue is about a memory leak in the
websocket handler.

Memory leak in websocket handler

Migrate to Node 20

gh issue edit 45.*--add-label.*priority:high


Update a Linear issue status to done

Update the Linear issue "ACM-101" (Implement OAuth2 PKCE flow) to mark
its status as "done". The implementation has been completed and merged.

Implement OAuth2 PKCE flow

Database migration script

Update CI pipeline

linear issue update ACM-101.*--status.*done


List Notion pages

List all pages in the Notion workspace. Show the page title, last edited time,
and parent database or page for each entry.

Engineering Runbook

Q1 OKRs

Onboarding Checklist

Incident Post-Mortem Template

API Design Guidelines

Engineering Runbook
Q1 OKRs
Onboarding Checklist
Incident Post-Mortem Template
API Design Guidelines


Create a Notion page

Create a new Notion page under the "Engineering Wiki" parent with the title
"Redis Caching Strategy". The page content should describe a caching approach
for the user service with TTL policies.

Engineering Runbook

Incident Post-Mortem Template

Engineering Wiki

Redis Caching Strategy

notion page create.*--parent.*Engineering Wiki.*--title.*Redis Caching Strategy


List Jira issues in a project

List all issues in the Jira project "INFRA" (Infrastructure). Show the issue
key, summary, status, assignee, and priority for each issue.

Infrastructure

Summary: Upgrade Kubernetes to 1.29

Summary: Set up Prometheus alerting rules

Summary: Migrate RDS from db.m5 to db.m6i

Summary: Configure CloudFront cache invalidation

Summary: Implement VPC peering for staging


Create a Jira issue

Create a new Jira issue in the "INFRA" project with summary "Set up
centralized log aggregation with Loki", type "Task", priority "High",
and assign it to "ops-bob".

Summary: Implement VPC peering for staging


Search Gmail for messages from a sender

Search Gmail for all emails from "security@github.com" received in the
last 30 days. Display the subject, date, and a snippet of each message.

Security advisory: CVE-2026-1234

A critical vulnerability has been identified in...

Dependabot alert: lodash prototype pollution

A new Dependabot alert has been created for...

Issue ACM-101 assigned to you

Secret scanning alert: API key exposed

A secret has been detected in your repository...

CVE-2026-1234
Dependabot alert
Secret scanning alert


List Google Calendar events for today

List all events on the primary Google Calendar for today (2026-03-12).
Show the event title, start time, end time, and attendees.

Daily Standup

Sprint Planning

1:1 with Manager

Architecture Review

Daily Standup
Sprint Planning
1:1 with Manager


List files in Google Drive

List all files in the Google Drive folder "Engineering/Architecture".
Show the file name, size, last modified date, and owner.

System Design v2.pdf
Database Schema.drawio
API Spec OpenAPI.yaml
Infrastructure Diagram.png
Migration Plan Q1.docx


Comment on a Linear issue

Add a comment to the Linear issue "ACM-102" (Database migration script)
with the text: "Migration tested successfully on staging. Ready for production
deployment. Rolling update strategy confirmed with ops team."

Database migration script

Schema changes drafted, running test suite.

Make sure to test with the staging dataset.

Update CI pipeline


Find urgent GitHub issues and post summary to Slack

Find all open GitHub issues in "acme-corp/web-platform" that have the label
"priority:critical" or "priority:high". Then compose a summary of these issues
and post it to the #engineering Slack channel with the format:
"Urgent Issues Report: N issues require attention" followed by a list.

Fix login redirect loop

Memory leak in websocket handler

Migrate to Node 20

SQL injection in search endpoint

Add dark mode toggle


Create Linear issues from Slack channel messages about bugs

Search the #incidents Slack channel for messages from the last 24 hours that
mention "bug" or "error". For each unique bug report found, create a
corresponding Linear issue in the "Platform" team with priority "high"
and status "triage".

incidents

Bug detected: Payment processing fails for amounts > $10,000

Error in user registration — email validation regex rejects valid TLDs

Deployed hotfix for the caching issue from yesterday

Bug report from customer: PDF export generates blank pages

Standup reminder: 2pm today

Existing issue


Sync GitHub issue labels with Linear issue priorities

For each open issue in the GitHub repo "acme-corp/web-platform" that has a
"linear:" prefixed label (e.g., "linear:ACM-101"), find the corresponding
Linear issue and update its priority to match the GitHub issue's priority
label. Map as follows: "priority:critical" -> urgent, "priority:high" -> high,
"priority:medium" -> medium, "priority:low" -> low.

Auth token expiry handling

API rate limiting

Fix CORS headers

Update docs

Logging improvements

Auth token expiry handling

API rate limiting

Fix CORS headers

Logging improvements

gh issue list.*--repo acme-corp/web-platform

linear issue update ACM-201.*--priority.*urgent

linear issue update ACM-202.*--priority.*medium

linear issue update ACM-203.*--priority.*high


Find unassigned Linear issues and notify team on Slack

Find all Linear issues in the "Platform" team that have status "todo" or
"in_progress" but have no assignee. Post a message to the #engineering
Slack channel listing these unassigned issues and asking team members
to pick them up.

Implement rate limiter middleware

Set up integration tests

Refactor auth module

Add health check endpoints

Database connection pooling


Create Notion summary from Linear project status

Retrieve the status of the Linear project "Q1 Platform Migration" including
all its issues and their current states. Create a Notion page under
"Engineering Wiki" titled "Q1 Platform Migration - Status Report" that
summarizes the project progress: total issues, completed vs in-progress vs
todo counts, and lists any blocked items.

Migrate user service to gRPC

Update API gateway routing

Database schema migration

Update client SDKs

Load testing new endpoints

Engineering Runbook

Engineering Wiki

linear issue list.*--project.*Q1 Platform Migration

Q1 Platform Migration - Status Report

notion page create.*--title.*Q1 Platform Migration.*Status Report


Find Jira issues blocked for more than 3 days and notify on Slack

Search the Jira project "INFRA" for issues with status "Blocked" that have
been in that status for more than 3 days. For each blocked issue, post a
notification to the #incidents Slack channel with the issue key, summary,
assignee, and how long it has been blocked.

Infrastructure

Summary: Upgrade load balancer firmware

Summary: Deploy new monitoring agent

Summary: Rotate SSL certificates

Summary: Set up backup replication

Summary: Network segmentation review


Search Gmail for meeting invites and create Linear tasks

Search Gmail for emails with subject containing "Action Items" or "Follow-up"
received in the last 7 days. Extract action items from these emails and create
corresponding Linear issues in the "Platform" team with appropriate priorities.

Meeting Action Items - Sprint Review 3/10

Action items from today's sprint review:
1. [HIGH] Investigate performance regression in search API
2. [MEDIUM] Update API documentation for v2 endpoints
3. [LOW] Clean up deprecated feature flags

Follow-up: Security Audit Discussion

Follow-up tasks:
1. [URGENT] Patch CVE-2026-5678 in auth library
2. [HIGH] Enable CSP headers on all endpoints

Lunch plans for Friday

Anyone want to try the new ramen place?

PR Review Requested

bob requested your review on PR #567

google gmail search.*(Action Items|Follow-up)


Find large files in Google Drive and post report to Slack

List all files in Google Drive that are larger than 50 MB. Create a summary
report with the file name, size, owner, and last modified date, then post
this report to the #engineering Slack channel with a message asking owners
to archive or clean up unused large files.


Cross-reference GitHub PRs with Linear issues

List all open pull requests in "acme-corp/web-platform" that reference a
Linear issue in their title or body (pattern: ACM-NNN). For each referenced
Linear issue, update its status to "in_progress" if it is currently "todo".
Report any PRs that reference non-existent Linear issues.

feat: Implement PKCE flow [ACM-501]

Implements the OAuth2 PKCE flow as described in ACM-501.

fix: CORS headers [ACM-502]

Fixes CORS header configuration per ACM-502.

chore: Update dependencies

Routine dependency updates, no Linear issue.

feat: Rate limiter [ACM-503]

Implements rate limiting middleware. Refs ACM-503.

fix: Session handling [ACM-999]

Fix session timeout. References ACM-999.

Implement OAuth2 PKCE flow

Fix CORS headers

Implement rate limiter

gh pr list.*--repo acme-corp/web-platform

linear issue update ACM-501.*--status.*in_progress

linear issue update ACM-503.*--status.*in_progress


Create Notion doc listing all Slack channel topics

List all public Slack channels in the workspace and collect their names,
topics, and member counts. Create a Notion page under "Company Resources"
titled "Slack Channel Directory" that organizes all channels into a
structured document with descriptions and member counts.

engineering

Engineering discussions, code reviews, technical decisions

incidents

Production incident coordination and post-mortems

hiring

Hiring pipeline updates and interview feedback

product

Product roadmap, feature requests, user feedback

Company Handbook

Company Resources

Slack Channel Directory

notion page create.*--title.*Slack Channel Directory


Incident response: find broken commit, create issue, assign on-call, notify Slack

A production incident has been reported. Investigate the GitHub repository
"acme-corp/web-platform" to find the most recent merged PR that touched
files in the "src/auth/" directory. Create a GitHub issue documenting the
incident and link it to that PR. Then find the on-call engineer from the
Linear team "Platform" (the one with the "oncall" label on their current
issue) and assign the GitHub issue to them. Finally, post an incident
notification to the #incidents Slack channel with the issue link, suspected
PR, and assigned engineer.

feat: Add session refresh logic

fix: Update user avatar upload

chore: Bump auth library version

docs: Update API reference

Existing tracking issue

On-call rotation week 11

Refactor error handling

Performance optimization

gh issue create.*--repo acme-corp/web-platform


Sprint planning: pull Linear backlog, create Notion sprint doc, notify team

Prepare for sprint planning. Pull all Linear issues from the "Platform"
team that are in "backlog" or "todo" status and have priority "high" or
"urgent". Create a Notion page under "Engineering Wiki" titled
"Sprint 12 Planning - 2026-03-12" that organizes these issues by priority,
includes estimated effort, and highlights any blocked dependencies.
Then post a message to the #engineering Slack channel announcing the sprint
planning doc is ready and listing the top 3 highest priority items.

Implement GraphQL subscriptions

Add OpenTelemetry tracing

Migrate to PostgreSQL 16

Implement circuit breaker pattern

Update API documentation

Add retry logic to external calls

Provision new database cluster

Engineering Wiki

Sprint 11 Retrospective


Cross-platform project sync: GitHub milestones to Linear projects to Notion

Synchronize project tracking across three platforms. First, list all open
GitHub milestones in "acme-corp/web-platform". For each milestone, find or
create the corresponding Linear project (matching by name). Update the
Linear project's target date to match the milestone's due date. Finally,
create a Notion page under "Project Tracking" that shows a unified view
of all projects with their GitHub milestone progress (open/closed issue
counts) and Linear project status.

v3.0 Release

Major version release with new auth system

Security Hardening

Address all findings from Q4 security audit

Performance Sprint

P95 latency reduction targets

v2.9 Release

Project Tracking

Archived Projects

linear project (update|create).*Security Hardening

linear project create.*Performance Sprint

notion page create.*--parent.*Project Tracking


Bug triage: GitHub issues to Linear issues, assign by labels, notify Slack

Perform a full bug triage workflow. Find all open GitHub issues in
"acme-corp/web-platform" with the "bug" label that don't have a
"linear:" label yet. For each bug, create a Linear issue in the
appropriate team based on GitHub labels ("auth" -> Security team,
"api" -> Platform team, "ui" -> Frontend team, default -> Platform).
Set priority based on other labels ("priority:critical" -> urgent,
"priority:high" -> high, otherwise medium). Add a "linear:ACM-XXX"
label back to each GitHub issue. Finally, post a triage summary to
#engineering on Slack listing all newly created Linear issues.

XSS vulnerability in search input

REST API returns 500 on empty payload

Button misalignment on mobile

Race condition in job queue

Implement dark mode

Token refresh bug [linear:ACM-501]

Token refresh bug


(kforge) Deploy artifact: list artifacts, trigger staging pipeline, check status

Using the kforge CLI, deploy the latest build artifact for the "web-platform"
service to the staging environment. First, list available artifacts to find
the most recent successful build. Then trigger a deployment pipeline for
staging using that artifact. Wait for the pipeline to reach a terminal state
and report the result. If the deployment fails, roll back to the previously
deployed version.


(flowctl) Create approval workflow: define steps, add gate, trigger run

Using the flowctl CLI, create a new approval workflow called
"production-deploy-approval" for the web-platform service. The workflow
should have three steps: (1) "security-scan" — automated security scanning,
(2) "qa-signoff" — manual approval gate requiring sign-off from the QA lead,
(3) "release-manager-approval" — manual approval gate requiring the release
manager. After creating the workflow, trigger a run of it with the context
of artifact version "2.3.1". Check that the workflow run was created
successfully and is in "pending" state waiting for the first step.


(alertmgr) Incident management: acknowledge alerts, create incident, escalate

Using the alertmgr CLI, handle a production incident. First, list all
firing alerts to understand the scope. Acknowledge all critical alerts
related to the "payment-service". Create a new incident titled
"Payment Service Degradation" with severity "P1" and link the acknowledged
alerts to it. Assign the incident to the on-call responder. If no on-call
responder is available, escalate to the engineering manager. Add a timeline
entry describing the initial findings.

Payment Service Degradation


(datapipe) Build ETL: connect source, create transform, set up sink, schedule

Using the datapipe CLI, build an ETL pipeline that extracts user activity
data from a PostgreSQL source, transforms it to compute daily active user
metrics, and loads the results into an Elasticsearch sink. Create a source
connection to the PostgreSQL database "analytics_db" on host
"db.internal:5432". Create a transform step that aggregates user events
by day and computes unique user counts. Create a sink connection to
Elasticsearch cluster "es.internal:9200" targeting the index
"user_metrics". Wire these into a pipeline called "daily-dau-pipeline"
and schedule it to run daily at 02:00 UTC.


(meshctl + alertmgr) Detect failing service, reroute traffic, create alert

A service mesh health check has detected issues. Using meshctl, check the
health of all services in the "production" mesh. For any service with error
rate above 5%, reroute its traffic to the canary deployment (weight 0%
to primary, 100% to canary). Then use alertmgr to create alerts for each
failing service and create an incident if more than one service is affected.
Add traffic rerouting details to the incident timeline.


(kforge + flowctl + slack) Full deployment: promote artifact, create approval gate, notify

Execute a full production deployment workflow using multiple tools.
First, use kforge to find the latest successful artifact for "web-platform"
that is currently deployed in staging. Verify the staging deployment is
healthy. Then use flowctl to create and trigger a "prod-release" approval
workflow with steps: automated security scan, manual QA approval, and
manual release manager approval. Use kforge to promote the staging artifact
to the production environment once the workflow is approved (simulate
approval). Finally, post deployment notifications to both #engineering
and #incidents Slack channels with the artifact version, deployment status,
and a link to the approval workflow run.