sprint-review — for Claude Code sprint-review, rhesis, community, for Claude Code, ide skills, generative-ai, llm-evaluation, llm-evaluation-framework, llmops, open-source

v1.0.0
GitHub

このスキルについて

適した場面: Ideal for AI agents that need generate a markdown changelog from github prs for sprint review meetings. ローカライズされた概要: Bring engineers, PMs, and domain experts together to generate tests, simulate (adversarial) conversations, and trace every failure to its root cause. It covers generative-ai, llm-evaluation, llm-evaluation-framework workflows. This AI agent skill supports Claude Code, Cursor, and

機能

Generate a markdown changelog from GitHub PRs for sprint review meetings.
Time range : last two weeks (14 days from today)
Author : the current GitHub user -- detect automatically via gh api user --jq .login
Both can be overridden if the user explicitly provides a different author or date.
Detect the current user (unless explicitly provided):

# Core Topics

for Claude Code generative-ai llm-evaluation llm-evaluation-framework llmops open-source
rhesis-ai rhesis-ai
[312]
[24]
Updated: 4/16/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
53
Canonical Locale
en
Detected Body Locale
en

適した場面: Ideal for AI agents that need generate a markdown changelog from github prs for sprint review meetings. ローカライズされた概要: Bring engineers, PMs, and domain experts together to generate tests, simulate (adversarial) conversations, and trace every failure to its root cause. It covers generative-ai, llm-evaluation, llm-evaluation-framework workflows. This AI agent skill supports Claude Code, Cursor, and

このスキルを使用する理由

推奨ポイント: sprint-review helps agents generate a markdown changelog from github prs for sprint review meetings. Bring engineers, PMs, and domain experts together to generate tests, simulate (adversarial) conversations

おすすめ

適した場面: Ideal for AI agents that need generate a markdown changelog from github prs for sprint review meetings.

↓ 実現可能なユースケース for sprint-review

ユースケース: Applying Generate a markdown changelog from GitHub PRs for sprint review meetings
ユースケース: Applying Time range : last two weeks (14 days from today)
ユースケース: Applying Author : the current GitHub user -- detect automatically via gh api user --jq .login

! セキュリティと制限

  • 制約事項: Requires repository-specific context from the skill documentation
  • 制約事項: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is sprint-review?

適した場面: Ideal for AI agents that need generate a markdown changelog from github prs for sprint review meetings. ローカライズされた概要: Bring engineers, PMs, and domain experts together to generate tests, simulate (adversarial) conversations, and trace every failure to its root cause. It covers generative-ai, llm-evaluation, llm-evaluation-framework workflows. This AI agent skill supports Claude Code, Cursor, and

How do I install sprint-review?

Run the command: npx killer-skills add rhesis-ai/rhesis/sprint-review. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for sprint-review?

Key use cases include: ユースケース: Applying Generate a markdown changelog from GitHub PRs for sprint review meetings, ユースケース: Applying Time range : last two weeks (14 days from today), ユースケース: Applying Author : the current GitHub user -- detect automatically via gh api user --jq .login.

Which IDEs are compatible with sprint-review?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for sprint-review?

制約事項: Requires repository-specific context from the skill documentation. 制約事項: Works best when the underlying tools and dependencies are already configured.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add rhesis-ai/rhesis/sprint-review. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use sprint-review immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

sprint-review

Install sprint-review, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Sprint Review

Generate a markdown changelog from GitHub PRs for sprint review meetings.

Defaults

  • Time range: last two weeks (14 days from today)
  • Author: the current GitHub user -- detect automatically via gh api user --jq .login

Both can be overridden if the user explicitly provides a different author or date.

Workflow

  1. Detect the current user (unless explicitly provided):
bash
1gh api user --jq .login
  1. Collect PRs using GitHub CLI (default: last 14 days):
bash
1gh pr list --author <username> --state all --search "created:>=<date>" --limit 100 \
2  --json number,title,state,createdAt,body,url \
3  | jq -r '.[] | "\(.number)|\(.title)|\(.state)|\(.createdAt)|\(.url)"'

  1. Fetch PR bodies for context on what each PR does (use --json body).

  2. Group PRs into two sections:

    • Features -- new capabilities, refactors, new providers, new APIs
    • Fixes -- bug fixes, dependency patches, config corrections, minor chores

  3. Consolidate similar PRs under a single description when they share the same goal (e.g. two PRs making different parts of the SDK async-first).

  4. Write the markdown file to docs/changelog-<username>.md using this format:

markdown
1## PR Changelog -- <username> (<start date> -- <end date>)
2
3### Features
4
5**Short heading**
6
7One-to-two sentence description.
8
9- [#<number> -- <title>](<url>)
10- [#<number> -- <title>](<url>) *(open/draft if not merged)*
11
12### Fixes
13
14**Short heading**
15
16One sentence description.
17
18- [#<number> -- <title>](<url>)

Formatting rules

  • Section headings: ### for Features / Fixes
  • Entry headings: bold text (not a markdown heading)
  • Descriptions: 1-2 sentences max, focus on what changed and why it matters
  • PR links: bulleted list with #<number> -- <title> as link text
  • Mark non-merged PRs with (open) or (draft)
  • No emojis

関連スキル

Looking for an alternative to sprint-review or another community skill for your workflow? Explore these related open-source skills.

すべて表示

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

カスタマイズ可能なウィジェットプラグインをprompts.chatのフィードシステム用に生成する

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

React フレームワーク

★ 138.4k
⑂ 0
ブラウザ

pr-review

Logo of pytorch
pytorch

Pythonにおけるテンソルと動的ニューラルネットワーク（強力なGPUアクセラレーション）

★ 98.6k
⑂ 0
開発者