harvest

Collecting GitHub PR data and generating work reports. Retrieves PR info via gh commands to auto-generate weekly/monthly reports and release notes. Use when work reporting or PR analysis is needed.

Jump to install

Repository: simota/agent-skills
Last source activity: July 29, 2026 at 01:32
Detected SKILL.md language: English
Stars: 71
Forks: 14

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/simota/agent-skills --skill harvest

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

28 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

chain

Auditing skill/plugin/MCP supply chains. Treats SKILL.md, bundled scripts, MCP server defs, hooks, and `.claude/` config as third-party software. Generates sha256 manifests, scans for Unicode Tag injection, detects curl-pipe + credential-exfil patterns, enforces third-party intake checklist, and pins MCP tool descriptions against rug-pulls. Use when auditing skill/MCP supply chain. Not for app SAST (Sentinel), CI/CD (Gear/Pipe), hook design (Latch), SKILL.md format (Gauge), or runtime exploit (Probe).

2026-08-10

latch

Proposing, configuring, debugging, and maintaining Claude Code hooks (PreToolUse/PostToolUse/Stop and other lifecycle events). Use when workflow automation, quality gates, or security enforcement via hooks is needed.

2026-08-10

nexus

Orchestrating specialist AI agent teams as a meta-coordinator. Decomposes requests into minimum viable chains, spawns each as an independent session in AUTORUN modes, and drives to final output. Use when a task spans multiple specialist domains, requires parallel agent execution, or needs hub-and-spoke routing across the skill ecosystem.

2026-08-10

View all from this repository

Harvest

Read GitHub PR history, aggregate it safely, and turn it into audience-fit reports. Harvest is read-only.

Trigger Guidance

Use Harvest when you need any of the following:

PR list retrieval with repository, period, author, label, or state filters

Weekly or monthly summaries for engineering work

Individual work reports based on merged PR history

Release notes or changelog-style summaries between tags or periods

Client-facing progress reports with estimated effort and charts

Quality trend reports that merge Judge feedback into PR activity

Narrative retrospectives or release commentary based on PR history

PR size distribution analysis (200 LOC target, 400 LOC ceiling benchmarks) with stacked PR recommendation when large PRs are persistent

DORA metric collection: 5 key metrics per DORA 2025 — throughput (Deployment Frequency, Lead Time for Changes, Failed Deployment Recovery Time) and instability (Change Failure Rate, Rework Rate) — plus Reliability as quasi-metric. Team profiling via 7 archetypes and per-metric percentile bands (Top 15% / Top 15-30% / Mid / Bottom), replacing the deprecated low/medium/high/elite cluster labels

Review cycle time reporting — measure from "ready for review" timestamp, not PR creation (draft PRs inflate cycle time otherwise). Break down into 4 phases: Coding (before PR), Pickup (PR created → first reviewer assigned), Review (first review action → approval), Merge (approval → merge). Phase-level breakdown pinpoints bottlenecks that aggregate cycle time hides

Rubber-stamping detection: flag when review lead time is low and uncorrelated with PR size

Route elsewhere when the task is primarily:

Real-time dashboard implementation → Pulse

Harvest

Read GitHub PR history, aggregate it safely, and turn it into audience-fit reports. Harvest is read-only.

Trigger Guidance

Use Harvest when you need any of the following:

PR list retrieval with repository, period, author, label, or state filters

Weekly or monthly summaries for engineering work

Individual work reports based on merged PR history

Release notes or changelog-style summaries between tags or periods

Client-facing progress reports with estimated effort and charts

Quality trend reports that merge Judge feedback into PR activity

Narrative retrospectives or release commentary based on PR history

PR size distribution analysis (200 LOC target, 400 LOC ceiling benchmarks) with stacked PR recommendation when large PRs are persistent

Rubber-stamping detection: flag when review lead time is low and uncorrelated with PR size

Route elsewhere when the task is primarily:

Real-time dashboard implementation → Pulse

Decision

Rule

Large queries

Gate defined in Boundaries → Ask First (>100 PRs). Rationale: GitHub REST API allows 5,000 req/hr authenticated; a 500-PR fetch with per_page=100 and --paginate costs only 5 requests — the ask-first gate is about scope confirmation and report shape, not raw rate-limit headroom

Cache freshness

Use prefer_cache by default; switch to force_refresh only when freshness matters more than API cost. Use ETags/If-Modified-Since headers to minimize API consumption

Graceful degradation

If fields are missing, lower report quality explicitly rather than fabricating data. Label degraded sections clearly

Work-hour calculation

Start with the implemented baseline formula, then apply optional refinement layers only when the audience needs them. Always output as ranges (e.g., 2-4h), never as single precise values

PR size classification

Small: ≤200 LOC, Medium: 201-400 LOC, Large: 401-1000 LOC, Oversized: >1000 LOC. Flag oversized PRs with 70% lower defect detection rate warning

First response time

Flag when median exceeds 1 business day. Google benchmark: max 1 business day for first review response

Cycle time measurement

Use "ready for review" timestamp as start, not PR creation. Draft PRs distort cycle time if measured from creation. Report 4-phase breakdown (Coding→Pickup→Review→Merge) to expose where time is lost

Pickup time benchmark

Elite teams: <6h pickup; strong teams: <13h. Flag when median pickup exceeds 1 business day

Total cycle time benchmark

Elite teams: <26h total cycle time (LinearB 2025). Good: <48h. Flag when team median exceeds 48h — total cycle time is the single most predictive metric for delivery throughput

Stacked PRs recommendation

When >30% of PRs exceed 400 LOC consistently, recommend stacked PRs as mitigation — teams using stacked PRs show ~20% more throughput with ~8% smaller median PR size, reducing review burden and merge queue wait

Rubber-stamping

Flag when median review lead time is low and uncorrelated with PR size — indicates reviewers may not be reading code

Release notes

Use Keep a Changelog categories and highlight breaking or deprecated changes. Automate via conventional commit type mapping (feat→Added, fix→Fixed, etc.). User-focused: explain what users gain, not raw commit messages

Quality metrics

Include context and actions; avoid vanity metrics and rankings. Combine 5 DORA key metrics (3 throughput + 2 instability per DORA 2025) plus Reliability quasi-metric with SPACE satisfaction/well-being signals. Use per-metric percentile bands and 7 team archetypes (not deprecated 4-tier clusters) for performance profiling

AI-period comparison

When comparing metrics across periods with different AI adoption levels, note that AI inflates individual PR counts while org delivery stays flat (DORA 2025)

PDF export

Prefer repo scripts and ASCII fallback over brittle ad-hoc export commands

Pagination strategy

Always use per_page=100 with gh api --paginate for automatic multi-page fetches. For GraphQL, use cursor-based pagination with first ≤100. GraphQL is more point-efficient for complex multi-field queries (2,000 pts/min vs 900 pts/min for REST per GitHub secondary rate limits). Store ETags per page, not per collection

Reference

Read this when...

reference/gh-commands.md

You need exact gh commands, field lists, date filters, or aggregation snippets.

reference/report-templates.md

You need canonical shapes for summary, detailed, individual, release-notes, or quality-trends reports.

reference/client-report-templates.md

You need client-facing report structure, charts, tables, or HTML/PDF packaging.

reference/work-hours.md

You need effort-estimation rules, file weights, range guidance, or LLM-assisted adjustments.

reference/pdf-export-guide.md

You need Markdown/HTML to PDF conversion, Mermaid handling, or repo export scripts.

reference/error-handling.md

You hit auth, rate-limit, network, API, or partial-data failures.

reference/caching-strategy.md

You need cache TTLs, invalidation, cleanup, or cache_policy behavior.

reference/outbound-handoffs.md

You need a handoff payload for Pulse, Canvas, Zen, Sherpa, Radar, Launch, or Guardian.

reference/retrospective-voice.md

You need a human narrative layer for a sprint retrospective, release commentary, or newsletter.

reference/engineering-metrics-pitfalls.md

You need guardrails for DORA/SPACE, vanity-metric avoidance, or burnout warnings.

reference/changelog-best-practices.md

You need changelog/release-note category rules and audience-fit writing.

reference/estimation-anti-patterns.md

You need caveats around LOC-based effort estimation and range reporting.

reference/reporting-anti-patterns.md

You need report-design guardrails, actionability checks, or gaming detection.

reference/dora-metrics.md

You need DORA 5-key metric percentile bands (DORA 2025), 3-throughput / 2-instability categorization, 7-archetype team profiling, measurement-window selection, gh/Insights integration, or SPACE complement for the dora recipe.

reference/okr-linkage.md

You need PR-to-Objective tagging conventions, KR progress narrative templates, Objective health scoring, or quarterly aggregation for the okr recipe.

reference/pr-stats-analysis.md

You need cycle-time decomposition, P50/P75/P90 reporting, Lorenz/Gini, bot allowlist, or large-PR risk thresholds for the prstats recipe.

_common/OPUS_5_AUTHORING.md

You are sizing the work report, deciding adaptive thinking depth at archetype/caveat handling, or front-loading window/scope/audience at COLLECT. Critical for Harvest: P3, P5.

reference/autorun-schema.md

You are emitting the AUTORUN _STEP_COMPLETE block — Harvest-specific Output/Next schema.

Recipe	Subcommand	Default?	When to Use	Read First
Weekly Report	`weekly`	✓	Weekly work report (PR aggregation and summary)	`reference/report-templates.md`
Monthly Report	`monthly`		Monthly report (includes DORA metrics)	`reference/report-templates.md`
Release Notes	`release`		Release notes generation (PR aggregation between tags)	`reference/changelog-best-practices.md`
Sprint Retro	`retro`		Retrospective aggregation and narrative	`reference/retrospective-voice.md`
DORA Deep-Dive	`dora`		DORA 5-key metric profile (3 throughput + 2 instability per DORA 2025) with 7-archetype team mapping and SPACE complement	`reference/dora-metrics.md`
OKR Linkage	`okr`		PR-to-Objective mapping and KR narrative for quarterly review	`reference/okr-linkage.md`
PR Stats Deep-Dive	`prstats`		Cycle time histogram, P50/P75/P90 latency, Lorenz curve, large-PR risk	`reference/pr-stats-analysis.md`

Mode	Use when	Default output
`Summary`	Need core PR statistics and category breakdown	`pr-summary-YYYY-MM-DD.md`
`Detailed List`	Need a full PR ledger for audit or tracking	`pr-list-YYYY-MM-DD.md`
`Individual`	Need one contributor's activity and estimated effort	`work-report-{username}-YYYY-MM-DD.md`
`Release Notes`	Need changelog-style reporting between releases or periods	`release-notes-vX.Y.Z.md`
`Client Report`	Need client-facing Markdown/HTML/PDF with effort and visuals	`client-report-YYYY-MM-DD.md` / `.html` / `.pdf`
`Quality Trends`	Need PR activity combined with `Judge` review signals	`quality-trends-YYYY-MM-DD.md`
`Retrospective Voice`	Need narrative commentary on a sprint or release	Append to another report or emit a standalone retrospective

Phase	Goal	Required actions Read
`SURVEY`	Lock scope	Confirm repository, period, filters, audience, and report mode `reference/`
`COLLECT`	Gather data	Use `gh` commands with `per_page=100` and `--paginate`, health checks, rate-limit monitoring, and cache policy appropriate to the request `reference/`
`ANALYZE`	Turn raw PRs into signal	Aggregate categories, sizes, timelines, effort estimates, quality, and trends. Apply PR size benchmarks (200/400/1000 LOC thresholds) `reference/`
`REPORT`	Build the artifact	Select the correct template, preserve caveats, pair quantity metrics with quality context, and keep filenames consistent `reference/`
`VERIFY`	Ensure report trustworthiness	Check completeness, validate no productivity rankings leak through, note degradations, and attach next actions `reference/`

Direction	Trigger	Contract
`Guardian -> Harvest`	Release prep needs release notes or tag-range summaries	`GUARDIAN_TO_HARVEST_HANDOFF`
`Judge -> Harvest`	Quality trend reporting needs review data	`JUDGE_TO_HARVEST_FEEDBACK`
`Trail -> Harvest`	Trend anomaly needs historical commit context	`TRAIL_TO_HARVEST_CONTEXT`
`Harvest -> Pulse`	PR metrics should feed KPI dashboards	`HARVEST_TO_PULSE_HANDOFF`
`Harvest -> Canvas`	Trend or timeline data needs visualization	`HARVEST_TO_CANVAS_HANDOFF`
`Harvest -> Zen`	PR titles or naming quality need analysis	`HARVEST_TO_ZEN_HANDOFF`
`Harvest -> Sherpa`	Large PRs need split recommendations	`HARVEST_TO_SHERPA_HANDOFF`
`Harvest -> Radar`	PR/test correlation needs coverage analysis	`HARVEST_TO_RADAR_HANDOFF`
`Harvest -> Launch`	Release notes are ready for release execution	`HARVEST_TO_LAUNCH_HANDOFF`
`Harvest -> Triage`	Data collection is critically blocked	`HARVEST_TO_TRIAGE_ESCALATION`

Signal	Approach	Primary output	Read next
default request	Standard Harvest workflow	analysis / recommendation	`reference/`
complex multi-agent task	Nexus-routed execution	structured handoff	`_common/BOUNDARIES.md`
unclear request	Clarify scope and route	scoped analysis	`reference/`

harvest

Install options

Review the source files

Harvest

Trigger Guidance

Harvest

Trigger Guidance

Core Contract

Boundaries

Always

Ask First

Never

Recipes

Subcommand Dispatch

Report Modes

Workflow

Critical Decision Rules

Routing And Handoffs

Output Routing

Output Requirements

Collaboration

Overlap Boundaries

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

`## NEXUS_HANDOFF`

name	harvest
description	Collecting GitHub PR data and generating work reports. Retrieves PR info via gh commands to auto-generate weekly/monthly reports and release notes. Use when work reporting or PR analysis is needed.

harvest

Source facts

Install options

Review the source files

More from this repository

Harvest

Trigger Guidance

More from this repository

Harvest

Trigger Guidance

Core Contract

Boundaries

Always

Ask First

Never

Recipes

Subcommand Dispatch

Report Modes

Workflow

Critical Decision Rules

Routing And Handoffs

Output Routing

Output Requirements

Collaboration

Overlap Boundaries

Reference Map

Operational

AUTORUN Support

Nexus Hub Mode

## NEXUS_HANDOFF

`## NEXUS_HANDOFF`