본문으로 건너뛰기
cccskills
무료GitHub에 공개

pr-review-sla

Check open GitHub pull requests for overdue reviews, inactivity, and requested changes without an author response. Send a single Slack summary identifying blockers and the people responsible for the next step, while leaving GitHub unchanged.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Daily PR review SLA sweep for {{target_repos}}. Flags PRs awaiting review past {{review_sla_hours}}h, stale PRs with no activity in {{stale_days}}d, and PRs sitting on unaddressed requested changes, then nudges the author or reviewer in {{alert_channel}} with what's blocking. Read-only against GitHub — never merges, closes, or approves.

연동 도구SlackGitHub

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Checking review deadlines each morning
  • Finding inactive pull requests
  • Identifying requested changes awaiting an author response
  • Sharing blockers across multiple repositories

포함된 파일(1)

  • SKILL.md4.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

<skill name="pr-review-sla"> <overview> Catch a stalled PR the morning it stalls, not the week someone notices. A daily cron spawns a fresh session with read-only access to GitHub through the `gh` CLI; this skill pulls every open PR across `{{target_repos}}` and checks each one against three independent rules — overdue for first review, stale with no activity, and carrying requested changes the author hasn't addressed — then nudges whoever owns the next move in {{alert_channel}}.

Proactive and schedule-driven; recomputes from GitHub's current state every run, with no memory of the prior day's nudges. </overview>

<when-to-load> - The daily cron fires the PR review sweep. - A human asks which PRs are overdue for review, stale, or blocked on unaddressed feedback. </when-to-load> <workflow>

Step 0 — Orient

# List every open PR across the configured repos.
gh pr list --repo {{target_repos}} --state open \
  --json number,title,url,author,createdAt,updatedAt,reviewRequests,reviews,comments,commits

Fresh session, no ledger — recompute everything from this pull. Repeat per repo if {{target_repos}} names more than one.

Step 1 — Pull the review detail per PR

gh pr view --repo {{target_repos}} <PR_NUMBER> \
  --json number,title,url,author,createdAt,updatedAt,reviewRequests,reviews,comments,commits

reviews gives each review's state (APPROVED, CHANGES_REQUESTED, COMMENTED) and timestamp; commits and comments give the last activity; reviewRequests gives who's currently asked to review.

Step 2 — Flag PRs awaiting review past the SLA

For each PR with an outstanding reviewRequests entry and no APPROVED or CHANGES_REQUESTED review from that reviewer since the request:

hours_waiting = now - max(createdAt, last review-request timestamp)

Flag if hours_waiting > {{review_sla_hours}}. Nudge target: the requested reviewer(s).

Step 3 — Flag stale PRs

For every open PR, take the most recent of: last commit, last comment, last review.

days_idle = now - max(last_commit, last_comment, last_review)

Flag if days_idle > {{stale_days}}. Nudge target: the author. A PR already flagged in Step 2 can also be flagged here if it independently qualifies — the two checks are separate signals, not mutually exclusive.

Step 4 — Flag unaddressed requested changes

For each PR whose most recent review is CHANGES_REQUESTED, check whether the author has pushed a commit or posted a comment since that review's timestamp. If not, flag it. Nudge target: the author.

CheckPasses (no nudge)Fails (nudge)
Overdue reviewReviewer submitted within SLANo review after {{review_sla_hours}}h
StaleAny activity within the windowNo activity for {{stale_days}}d
Unaddressed changesAuthor pushed/replied after the reviewSilence since CHANGES_REQUESTED

Step 5 — Write the nudge

For every PR that trips at least one rule, write one line: the PR title and link, which rule(s) it tripped, and how long it's been in that state, e.g. "Awaiting review 3d (SLA 24h) — @reviewer" or "Stale 6d, no activity — @author" or "Changes requested 4d ago, not yet addressed — @author". A PR that trips more than one rule gets one entry listing all of them, not a duplicate nudge per rule.

Step 6 — Post to Slack

Post exactly one summary message to {{alert_channel}} for the whole sweep, grouped by rule (overdue for review / stale / unaddressed changes), each entry tagging the person it's nudging. This is a fresh session — there is no prior list to diff against, so the whole sweep is recomputed and reposted every day.

</workflow> <guardrails> - **Read-only, always.** Every GitHub call is a read (`gh pr list`, `gh pr view`, `gh api` GET). Never merge, close, approve, or dismiss a review, even if `GH_TOKEN` would technically allow it. - **One output.** The Slack post to {{alert_channel}} is the only thing that leaves the sandbox. No PR comments, no direct messages, no GitHub writes. - **No memory between runs.** Each run is a fresh session; recompute every PR's state from GitHub rather than assuming anything from the prior day's nudges. - **Scoped secret.** `GH_TOKEN` is injected as an environment variable at runtime, scoped to read access and to this agent's grant. - **People decide, not the agent.** The nudge flags what's blocking; a human reviews, pings, or closes the PR themselves. </guardrails> </skill>

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing GitHub repository access requests from Slack
  • Preparing AWS IAM permissions for a specific task
  • Routing sensitive access requests for additional review
kortix-ai/suna2만2026년 10월 23일 업데이트

Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Research a prospective customer before outreach
  • Prepare background information for meeting attendees
  • Compare a competitor's products and positioning
kortix-ai/suna2만2026년 10월 23일 업데이트

Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking whether campaign budgets are being spent on schedule
  • Investigating rising acquisition costs or falling ad returns
  • Finding ads and keywords that spend without converting
kortix-ai/suna2만2026년 10월 23일 업데이트

Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Automate form entry and page navigation
  • Capture screenshots and extract page data
  • Explore web apps for bugs
kortix-ai/suna2만2026년 10월 23일 업데이트

Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking incoming invoices against purchase orders
  • Finding duplicate invoices and likely resends
  • Reviewing unit prices and remaining order balances
kortix-ai/suna2만2026년 10월 23일 업데이트

billing

무료

Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Update billing logic and its specification together
  • Review how trials and enterprise contracts are handled
  • Find the code that defines prices and allowances
kortix-ai/suna2만2026년 10월 23일 업데이트

kortix-ai의 스킬 모두 보기

이 스킬의 문제 신고