majiayu000
majiayu000/claude-skill-registry
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/majiayu000/claude-skill-registry --skill review-chamber命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | review-chamber |
| description | Capture and retrieve PR review knowledge in project memory palaces |
| Triggers | memory, project, capture, retrieve, review |
| version | 1.0.0 |
| triggers | ["pr review completed","knowledge capture requested","review patterns query","past decisions lookup"] |
| usage_patterns | [{"capture-review":"After PR review completion, capture significant findings"},{"search-decisions":"Find past architectural decisions"},{"pattern-lookup":"Retrieve recurring issues and solutions"},{"standards-reference":"Access quality standards from past reviews"}] |
| dependencies | ["memory-palace:knowledge-intake","sanctum:pr-review"] |
| modules | ["capture-workflow.md","evaluation-criteria.md","search-patterns.md"] |
Capture, organize, and retrieve knowledge from PR reviews within project memory palaces.
The Review Chamber is a dedicated room within each project palace that stores valuable knowledge extracted from PR reviews. It transforms ephemeral PR discussions into persistent, searchable institutional memory.
review-chamber/
├── decisions/ # Architectural choices from PR discussions
├── patterns/ # Recurring issues and their solutions
├── standards/ # Quality bar examples and coding conventions
└── lessons/ # Post-mortems and learnings
Verification: Run the command with --help flag to verify availability.
After a PR review completes, evaluate findings for knowledge capture:
## Knowledge Detection Checklist
For each finding from sanctum:pr-review, evaluate:
- [ ] **Novelty**: Is this a new pattern or first occurrence?
- [ ] **Applicability**: Will this affect future PRs in this area?
- [ ] **Durability**: Is this architectural (capture) or tactical (skip)?
- [ ] **Connectivity**: Does it link to existing palace rooms?
Verification: Run the command with --help flag to verify availability.
Route findings to appropriate subrooms:
| Finding Type | Target Room | Criteria |
|---|---|---|
| Architectural choice | decisions/ | BLOCKING + architectural context |
| Recurring issue | patterns/ | Seen before or likely to recur |
| Quality example | standards/ | Exemplifies coding standards |
| Learning/insight | lessons/ | Retrospective or post-mortem |
Create structured entry with:
---
source_pr: "#42 - Add authentication"
date: 2025-01-15
participants: [author, reviewer1, reviewer2]
palace_location: review-chamber/decisions
related_rooms: [workshop/auth-patterns, library/security-adr]
tags: [authentication, jwt, security]
---
## Decision Title
### Decision
Chose JWT tokens over server-side sessions.
### Context (from PR discussion)
- Reviewer asked: "Why not use sessions?"
- Author explained: stateless scaling requirements
- Discussion refined: added refresh token rotation
### Captured Knowledge
- **Pattern**: JWT + refresh tokens for stateless auth
- **Tradeoff**: Complexity vs. horizontal scaling
- **Application**: Use for all API authentication
### Connected Concepts
- [[auth-patterns]] - Updated with JWT best practices
- [[security-adr-003]] - Referenced this decision
Verification: Run the command with --help flag to verify availability.
After capture, update related palace rooms:
# Automatic: sanctum:pr-review triggers capture
/pr-review 42
# → Review posted to GitHub
# → Knowledge capture evaluates findings
# → Significant decisions stored in review-chamber
# Manual: Explicitly capture from PR
/review-room capture 42 --room decisions
Verification: Run the command with --help flag to verify availability.
# Find authentication decisions
/review-room search "authentication" --room decisions
# Find patterns in a specific area
/review-room search "error handling" --room patterns --tags api
# List recent entries
/review-room list --limit 10 --room standards
Verification: Run the command with --help flag to verify availability.
When starting work in a code area:
## Relevant Review Knowledge
Starting work in `auth/` directory...
**Past Decisions:**
- [#42] JWT token decision → decisions/jwt-over-sessions
- [#67] Rate limiting pattern → patterns/api-throttling
**Quality Standards:**
- [#55] Error response format → standards/api-errors
**Known Patterns:**
- [#38] Token refresh edge case → patterns/token-refresh-race
Verification: Run the command with --help flag to verify availability.
The review-chamber integrates after Phase 6 (Generate Report):
**Verification:** Run the command with `--help` flag to verify availability.
Phase 6: Generate Report
↓
[HOOK] Evaluate findings for knowledge capture
↓
For each significant finding:
├── Classify into room type
├── Create ReviewEntry
├── Add to project palace
└── Update connections
↓
Phase 7: Post to GitHub
Verification: Run the command with --help flag to verify availability.
Uses the same evaluation framework:
| Criterion | Weight | PR Review Application |
|---|---|---|
| Novelty | 25% | New pattern or first occurrence |
| Applicability | 30% | Affects future PRs in this area |
| Durability | 20% | Architectural vs tactical |
| Connectivity | 15% | Links to existing rooms |
| Authority | 10% | Senior reviewer or domain expert |
Extends search to include review-chamber:
python scripts/palace_manager.py search "authentication" \
--palace project-name \
--room review-chamber \
--type semantic
Verification: Run python --version to verify Python environment.
# Capture knowledge from PR
/review-room capture <pr_number> [--room <room_type>] [--tags <tags>]
# Search review chamber
/review-room search "<query>" [--room <room_type>] [--tags <tags>]
# List entries
/review-room list [--room <room_type>] [--limit N]
# View entry details
/review-room view <entry_id>
# Export for documentation
/review-room export [--format markdown|json] [--room <room_type>]
# Statistics
/review-room stats [--palace <palace_id>]
Verification: Run the command with --help flag to verify availability.
Command not found Ensure all dependencies are installed and in PATH
Permission errors Check file permissions and run with appropriate privileges
Unexpected behavior
Enable verbose logging with --verbose flag