personal-assistant-review

Review personal-assistant Obsidian plugin code for release-blocking risks.

149|8|Updated Jun 17, 2022
One-click install
npx skills add https://github.com/edonyzpc/personal-assistant --skill personal-assistant-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: personal-assistant-review
Source: https://github.com/edonyzpc/personal-assistant/tree/main/.agents/skills/personal-assistant-review
Command: npx skills add https://github.com/edonyzpc/personal-assistant --skill personal-assistant-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews for the personal-assistant Obsidian plugin often miss critical risks like state concurrency bugs, privacy leaks, and Obsidian ecosystem compatibility breaks that cause user-facing failures post-release.

Core Features & Use Cases

  • Structured Review Lanes: Splits reviews into functional correctness, spec/docs alignment, Obsidian compatibility, UI/UX accessibility, and performance/safety checks to cover all high-impact risk areas.
  • Second-Layer Risk Scanning: Goes beyond surface bugs to identify hidden side effects, edge cases, and future maintenance risks that could cause failures after release.
  • Use Case: Use this skill when preparing a PR or release for the personal-assistant plugin to catch release-blocking issues before merging, avoiding post-release user complaints and rollbacks.

Quick Start

Ask the AI to review the current uncommitted changes or PR diff for the personal-assistant Obsidian plugin using project-specific risk lanes and severity rules.

Frequently Asked Questions about personal-assistant-review

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

FAQPage Schema
How do I perform a risk-focused code review for an Obsidian plugin before release?

A risk-focused code review for an Obsidian plugin evaluates PR diffs and uncommitted changes across functional correctness, ecosystem compatibility, UI/UX accessibility, and performance safety to catch release-blocking bugs before merging.

What is second-layer risk scanning in code reviews?

Second-layer risk scanning identifies hidden side effects, edge cases, and future maintenance risks beyond surface bugs. It detects post-release failures by evaluating state concurrency issues and future risks that cause user-facing breaks.

How do I check release readiness for Obsidian plugin updates across desktop and mobile?

Release readiness checks enforce project-specific severity rules and subagent lane routing to identify compatibility breaks across desktop and mobile Obsidian versions, ensuring your plugin update avoids post-release rollbacks.

How do I detect privacy leaks and state concurrency bugs in Obsidian plugin code?

Detect privacy leaks and state concurrency bugs by applying structured review lanes that scan for product contract compliance and hidden side effects, pinpointing release-blocking issues within uncommitted changes or PR diffs.

Can I use automated code reviews on uncommitted changes for the personal-assistant Obsidian plugin?

Yes, you can review uncommitted changes or PR diffs for the personal-assistant Obsidian plugin by applying structured review lanes and severity rules to catch release-blocking issues before merging.

What are the limitations of relying on manual code reviews for Obsidian plugins?

Manual code reviews often miss critical risks like state concurrency bugs, privacy leaks, and Obsidian ecosystem compatibility breaks, which cause user-facing failures post-release without structured, risk-focused automated scanning.