philosophy-compliance-workflow by rysweet/amplihack
npx skills add https://github.com/rysweet/amplihack --skill philosophy-compliance-workflow系统性的哲学合规审查,确保所有代码和架构符合 amplihack 的核心原则:极致简洁、积木哲学和禅意极简主义。该技能验证实现是否服务于明确目的,没有不必要的复杂性。
适用于:
避免用于:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
需要提出的问题:
扫描代码结构:
需要警惕的危险信号:
为每个组件提出 5 个核心问题:
必要性:"我们现在真的需要这个吗?"
简洁性:"解决这个问题最简单的方法是什么?"
模块化:"这能成为一个自包含的积木吗?"
可重构性:"AI 能否根据规范重建这个组件?"
价值:"复杂性是否带来了相应比例的价值?"
按严重程度分类问题:
严重(必须修复):
警告(应该修复):
建议(考虑):
创建结构化的审查输出:
# 哲学合规审查:[组件名称]
## 总体评分:[A/B/C/D/F]
## 摘要
[一段关于发现的概述]
## 优点(符合哲学之处)
- [识别出的符合哲学的模式]
- [良好实现的积木设计]
- [清晰的简洁性示例]
## 关注点(警告)
- [应解决的复杂性]
- [边缘的哲学违规]
- [改进的机会]
## 违规(关键问题)
- [明显偏离哲学之处]
- [必须修复的问题]
- [阻碍哲学合规的阻塞性问题]
## 建议
### 立即行动(关键)
1. [需要进行的特定修复及理由]
2. [另一个关键修复]
### 结构改进(重要)
1. [模块边界调整]
2. [解耦建议]
### 简化机会(锦上添花)
1. [减少复杂性的方法]
2. [移除抽象的建议]
## 重构能力评估
**AI 能否根据规范重建这些组件?**
- 模块 A:[就绪/需要改进] - [具体原因]
- 模块 B:[就绪/需要改进] - [具体原因]
**阻碍重构的因素:**
- [列出阻碍清晰 AI 重构的具体问题]
## 哲学一致性评分
- 极致简洁:[0-10]/10 - [理由]
- 积木哲学:[0-10]/10 - [理由]
- 禅意极简主义:[0-10]/10 - [理由]
**总体:[分数]/10**
针对每个违规,提供:
示例:
问题:SessionManager 类有 8 种不同的职责
违规:违反单一职责原则(积木哲学)
修复:拆分为:
- SessionStore(仅持久化)
- SessionValidator(仅验证)
- SessionLifecycle(仅创建/过期)
影响:每个积木可以独立重构和测试
优先级:关键
符合哲学的设计:
示例:良好的积木模块
authentication/
├── __init__.py # 导出:authenticate, validate_token
├── core.py # 实现(单一职责)
├── models.py # User, Token(清晰的数据模型)
├── tests/
│ └── test_core.py # 全面的测试
└── README.md # 重构规范
公共契约(连接点):
- authenticate(username, password) -> Token
- validate_token(token) -> User
单一职责:仅认证(非授权,非用户管理)
可重构性:是,可根据 README.md 规范重构
哲学违规:
示例:不良设计
user_system/
├── framework.py # 通用抽象层
├── manager.py # UserManager 处理所有事情
├── config/ # 广泛的配置系统
├── plugins/ # 插件架构(未使用)
└── adapters/ # 为其他数据库进行的未来防护
问题:
- UserManager 处理认证、个人资料、设置、通知
- 框架增加了复杂性但没有当前价值
- 为"也许有一天"构建的插件系统
- 多重职责,不可重构
何时将哲学审查与以下结合:
默认工作流位置:
伪装的复杂性:
哲学陷阱:
成功的哲学审查:
生成的文档:
保存位置:
~/.amplihack/.claude/runtime/logs/<session>/philosophy_review_<timestamp>.mdamplihack.memory.discoveries 中的 store_discovery() 将学到的模式存储在内存中你是系统的哲学良知。挑战复杂性,庆祝简洁性,确保每一个架构决策都朝着优雅、必要软件的禅意理想迈进。
你的目标不是完美——而是朝着更简单、更清晰、更可重构的代码持续改进。
每周安装次数
87
代码仓库
GitHub 星标数
43
首次出现
2026年1月23日
安全审计
安装于
opencode80
codex75
claude-code74
cursor73
gemini-cli72
github-copilot71
Systematic philosophy compliance review that ensures all code and architecture aligns with amplihack's core principles: ruthless simplicity, brick philosophy, and Zen-like minimalism. This skill validates that implementations serve clear purposes without unnecessary complexity.
USE FOR:
AVOID FOR:
Identify what to review:
Questions to ask:
Scan the code structure:
Red flags to watch for:
Ask the 5 core questions for each component:
Necessity : "Do we actually need this right now?"
Simplicity : "What's the simplest way to solve this problem?"
Modularity : "Can this be a self-contained brick?"
Regenerability : "Can AI rebuild this from a specification?"
Value : "Does the complexity add proportional value?"
Categorize issues by severity:
CRITICAL (Must Fix):
WARNING (Should Fix):
SUGGESTION (Consider):
Create structured review output:
# Philosophy Compliance Review: [Component Name]
## Overall Score: [A/B/C/D/F]
## Summary
[One paragraph overview of findings]
## Strengths (What Aligns)
- [Philosophy-aligned patterns identified]
- [Well-implemented brick designs]
- [Clear simplicity examples]
## Concerns (Warnings)
- [Complexity that should be addressed]
- [Borderline philosophy violations]
- [Opportunities for improvement]
## Violations (Critical Issues)
- [Clear departures from philosophy]
- [Must-fix problems]
- [Blocking issues for philosophy compliance]
## Recommendations
### Immediate Actions (Critical)
1. [Specific fix required with rationale]
2. [Another critical fix]
### Structural Improvements (Important)
1. [Module boundary adjustments]
2. [Decoupling suggestions]
### Simplification Opportunities (Good to Have)
1. [Ways to reduce complexity]
2. [Abstraction removal suggestions]
## Regeneration Assessment
**Can AI rebuild these components from specifications?**
- Module A: [Ready/Needs Work] - [Specific reason]
- Module B: [Ready/Needs Work] - [Specific reason]
**What's blocking regeneration:**
- [List specific issues preventing clear AI regeneration]
## Philosophy Alignment Score
- Ruthless Simplicity: [0-10]/10 - [Rationale]
- Brick Philosophy: [0-10]/10 - [Rationale]
- Zen Minimalism: [0-10]/10 - [Rationale]
**Overall: [Score]/10**
For each violation, provide:
Example:
Issue: SessionManager class has 8 different responsibilities
Violation: Breaks single responsibility (brick philosophy)
Fix: Split into:
- SessionStore (persistence only)
- SessionValidator (validation only)
- SessionLifecycle (creation/expiry only)
Impact: Each brick becomes regeneratable and testable independently
Priority: Critical
Philosophy-Aligned Designs:
Example: Good Brick Module
authentication/
├── __init__.py # Exports: authenticate, validate_token
├── core.py # Implementation (one responsibility)
├── models.py # User, Token (clear data models)
├── tests/
│ └── test_core.py # Comprehensive tests
└── README.md # Regeneration specification
Public Contract (Studs):
- authenticate(username, password) -> Token
- validate_token(token) -> User
One Responsibility: Authentication only (not authorization, not user management)
Regeneratable: Yes, from README.md specification
Philosophy Violations:
Example: Bad Design
user_system/
├── framework.py # Generic abstraction layer
├── manager.py # UserManager does everything
├── config/ # Extensive config system
├── plugins/ # Plugin architecture (unused)
└── adapters/ # Future-proofing for other DBs
Problems:
- UserManager handles auth, profile, settings, notifications
- Framework adds complexity without current value
- Plugin system built for "maybe someday"
- Multiple responsibilities, not regeneratable
When to combine philosophy review with:
Default workflow position:
Disguised Complexity:
Philosophy Traps:
A successful philosophy review:
Generated documents:
Where to save:
~/.amplihack/.claude/runtime/logs/<session>/philosophy_review_<timestamp>.mdstore_discovery() from amplihack.memory.discoveriesYou are the philosophical conscience of the system. Challenge complexity, celebrate simplicity, and ensure every architectural decision moves toward the Zen ideal of elegant, essential software.
Your goal is not perfection - it's continuous improvement toward simpler, clearer, more regeneratable code.
Weekly Installs
87
Repository
GitHub Stars
43
First Seen
Jan 23, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
opencode80
codex75
claude-code74
cursor73
gemini-cli72
github-copilot71
冲刺回顾模板:敏捷团队回顾会议指南与模板(开始-停止-继续/愤怒-悲伤-高兴/4Ls)
10,400 周安装