skills.rest
kage1020
kage1020COMMUNITY
Explore all skills by this author →
Website𝕏@kage1020GitHub

philosophy-review

Evaluate code diffs against UX constraints and engineering principles.

Updated Mar 15, 2026
Search Tags:#philosophy#engineering#principles#quality-assurance#ux#code-review#review-process
One-click install
npx skills add https://github.com/kage1020/dotfiles --skill philosophy-review-kage1020
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: philosophy-review
Source: https://github.com/kage1020/dotfiles/tree/main/dot_claude/skills/philosophy-review
Command: npx skills add https://github.com/kage1020/dotfiles --skill philosophy-review-kage1020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that code changes conform to a user-centered philosophy by systematically evaluating diffs against a defined set of UX constraints and engineering principles, surfacing violations and improvement proposals.

Core Features & Use Cases

  • Phase-based static and dynamic reviews (Phase 1 static code reading and Phase 2 browser-based checks when needed) aligned with a six-principle framework.
  • Automated reporting of violations, concerns, and suggested improvements to guide PR reviews and post-implementation retrospectives.
  • Clear decision criteria and actionable guidance to keep changes user-first and technically sound.

Quick Start

Submit the code diff you want reviewed and ask for a philosophy-style review.

Frequently Asked Questions about philosophy-review

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

FAQPage Schema
How do I review code changes for UX alignment and engineering principles?▼

To review code changes for UX alignment, submit your code diff to trigger a philosophy-style review. The process evaluates diffs against UX constraints and engineering principles, surfacing violations and improvement proposals.

What is a static-dynamic code review workflow?▼

A static-dynamic code review workflow combines Phase 1 static code reading with Phase 2 browser-based checks. This two-phase approach systematically evaluates code changes for user-centric, principle-driven compliance.

How do I structure a PR review report for engineering principle violations?▼

To structure a PR review report for engineering principle violations, use a structured format that captures violations, concerns, and suggested improvements. This guides PR reviews and post-implementation retrospectives with clear decision criteria.

Can I use principle-driven evaluation for project retrospectives?▼

Yes, you can use principle-driven evaluation for project retrospectives. The review process applies a six-principle framework to assess code changes, providing actionable guidance to keep updates user-first and technically sound.

Does this code review process require browser-based checks for every pull request?▼

No, browser-based checks are not required for every pull request. The review workflow uses Phase 1 static code reading by default, applying Phase 2 browser-based checks only when needed to verify dynamic UX constraints.

Related Skills

Explore More Software Engineering Skills→
hidemaro-nsketchhidemaro-nsketch

context-loader

Load project context from the .claude directory for OpenCLI.

Community
Intermediate
tobihagemanntobihagemann
399

finalize

Automate staging, testing, code simplification, AI review, and pull request generation.

Community
Advanced
mizunashi-manamizunashi-mana
5

autodev-create-pr

Create GitHub pull requests from current branch changes via shell commands.

Community
Intermediate
raybargasraybargas

Global Coding Style

Detect and fix coding style violations across multi-language repositories.

Community
Basic