Skip to content
Back to skills

Review Comment Style Mining

ASecurity

Use when mining PR review comments and text diffs for reusable writing, documentation, tone, and editorial improvement patterns.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 6, 2026
ai-agentsgitdocumentation

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add yeaight7/agent-powerups --skill review-comment-style-mining --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Review Comment Style Mining?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Review Comment Style Mining
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yeaight7-review-comment-style-mining-agent-powerups/badge)](https://www.skillsdirectory.com/skills/yeaight7-review-comment-style-mining-agent-powerups)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: review-comment-style-mining
description: Use when mining PR review comments and text diffs for reusable writing, documentation, tone, and editorial improvement patterns.
---

# Review Comment Style Mining

## When To Use

- User asks what writing feedback a PR received.
- Need to compare draft vs final docs, blog posts, prompts, or README text.
- Need recurring style lessons from reviewer comments.

## Requirements / Checks

- Confirm `gh` availability and auth before fetching private PR data.
- Ask before contacting GitHub or reading private repo content.
- Prefer bounded text formats: `.md`, `.mdx`, `.txt`, `.rst`.
- Cap large file diffs before sending to any model.

## Workflow

1. Identify PR URL or `owner/repo` plus PR number.
2. Extract inline suggestions, plain feedback, and changed text file evolution.
3. Separate mechanical edits from reviewer rationale.
4. Compare first draft and final text by section.
5. Group lessons by clarity, precision, tone, structure, grammar, and content.
6. Return a concise style guide the author can reuse.

## Safety Constraints

- Do not expose private PR content outside the local session without approval.
- Do not quote long proprietary text; summarize changes and cite file paths/permalinks when safe.
- Do not run broad GitHub fetches; scope to one PR unless user asks wider.

## Validation / Done Criteria

- Output distinguishes explicit suggestions from inferred style lessons.
- Each lesson is tied to at least one review comment or text change.
- Large file content is truncated or summarized.

## References

- `references/editorial-analysis-template.md`

Files in this skill

  • SKILL.md1.6 KB
  • references/editorial-analysis-template.md816 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…