skills.rest
edonyzpc
edonyzpcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

personal-assistant-review-followup

Classify code review findings into release-blocking and optional categories.

149|8|Updated Jun 17, 2022
Search Tags:#code review#regression testing#triage#personal-assistant#severity classification#fix validation#obsidian plugin
One-click install
npx skills add https://github.com/edonyzpc/personal-assistant --skill personal-assistant-review-followup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: personal-assistant-review-followup
Source: https://github.com/edonyzpc/personal-assistant/tree/main/.agents/skills/personal-assistant-review-followup
Command: npx skills add https://github.com/edonyzpc/personal-assistant --skill personal-assistant-review-followup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a code review of the personal-assistant repository, it is easy to waste time on low-priority polish comments, miss real release risks, or over-fix non-critical issues. This Skill eliminates that inefficiency by clearly separating real problems from optional improvements.

Core Features & Use Cases

  • Finding Classification: Automatically categorize review findings into must-fix, should-fix-now, and defer buckets based on release risk, safety, and product contract impact.
  • Decision Support: Provide structured lenses for architecture, program, and product decisions when findings require input before implementation.
  • Safe Implementation & Validation: Implement only user-confirmed fixes, add regression tests for accepted issues, and run focused validation checks to avoid over-claiming functionality.
  • Use Case: After a team or human code review of the personal-assistant Obsidian plugin, use this Skill to quickly identify which findings block release, which need product decisions, and safely implement only the necessary fixes.

Quick Start

Use the personal-assistant-review-followup skill to triage the latest code review findings for the personal-assistant repository, decide which fixes to implement, and validate the changes.

Frequently Asked Questions about personal-assistant-review-followup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage code review findings to separate release-blocking issues from optional polish?▼

Triage code review findings by categorizing them into must-fix, should-fix-now, and defer buckets based on release risk, safety, and product contract impact. This separates real release risks from optional improvements.

How do I implement confirmed fixes from a code review and validate the results?▼

Implement confirmed fixes by selectively applying user-accepted changes, adding regression tests for those accepted issues, and running focused validation checks without over-claiming app runtime behavior.

What is the best way to classify the severity of code review findings for a plugin release?▼

Classify code review finding severity by evaluating release risks, safety implications, and product contract impact. This process helps separate release-blocking issues from optional polish.

Does this code review triage process support adding regression tests for accepted fixes?▼

Yes, the code review triage process supports adding regression tests for accepted issues. It implements user-confirmed fixes and runs focused validation checks to ensure safe implementation.

How do I handle code review findings that require product or architecture decisions before implementation?▼

Handle code review findings requiring decisions by applying structured lenses for architecture, program, and product decisions. This provides decision support before implementing confirmed fixes.

When should I avoid over-claiming app runtime behavior during fix validation?▼

Avoid over-claiming app runtime behavior during fix validation by running only focused validation checks on accepted issues. This ensures you validate implemented fixes without asserting unrelated functionality.

Related Skills

Explore More Software Engineering Skills→
dimsourdimsour
2

dotnet:triage

Convert .NET code review findings into a prioritized task list grouped by severity.

Community
Intermediate
edonyzpcedonyzpc
149

obsidian-test-vault-smoke

Validate Obsidian plugin changes via tiered end-to-end smoke tests.

Community
Advanced
cwijayasundaracwijayasundara
3

harness-core

Automate build, test, deployment, and code review in CI/CD pipelines.

Community
Advanced
lklimeklklimek
1

triage-findings

Classify code review findings in a browser and update report.json.

Community
Advanced