176 lines
4.1 KiB
Markdown
176 lines
4.1 KiB
Markdown
# Review Checklist
|
|
|
|
> Template for structured content review. Use with `/review` command.
|
|
|
|
## Article Info
|
|
|
|
- **Title**: {{title}}
|
|
- **Slug**: {{slug}}
|
|
- **Status**: {{status}}
|
|
- **Review Date**: {{date}}
|
|
|
|
---
|
|
|
|
## 1. Structure Review (结构审)
|
|
|
|
### 1.1 Logic Flow
|
|
- [ ] Opening hooks reader effectively
|
|
- [ ] Main argument has clear progression
|
|
- [ ] Transitions between sections are smooth
|
|
- [ ] Conclusion reinforces key points
|
|
- [ ] No logical gaps or jumps
|
|
|
|
### 1.2 Paragraph Structure
|
|
- [ ] Each paragraph has single main idea
|
|
- [ ] Paragraphs are appropriately sized (3-7 sentences)
|
|
- [ ] Topic sentences are clear
|
|
- [ ] Supporting details are relevant
|
|
|
|
### 1.3 Information Hierarchy
|
|
- [ ] Headings reflect content accurately
|
|
- [ ] Important information is emphasized
|
|
- [ ] Subheadings break up long sections
|
|
- [ ] Visual elements support structure
|
|
|
|
**Issues Found**:
|
|
```
|
|
# List issues as: [{id, severity, description}]
|
|
# Example:
|
|
# - id: S1, severity: medium, description: "Section 3 lacks transition to Section 4"
|
|
```
|
|
|
|
---
|
|
|
|
## 2. Factual Review (事实审)
|
|
|
|
### 2.1 Data Accuracy
|
|
- [ ] All statistics have sources
|
|
- [ ] Numbers are correctly cited
|
|
- [ ] Claims are verifiable
|
|
- [ ] No fabricated data
|
|
|
|
### 2.2 Reference Quality
|
|
- [ ] Source URLs are accessible
|
|
- [ ] Quotes are accurate
|
|
- [ ] Citations follow consistent format
|
|
- [ ] No broken or outdated references
|
|
|
|
### 2.3 Technical Accuracy
|
|
- [ ] Technical terms used correctly
|
|
- [ ] Code examples work as described
|
|
- [ ] API references are current
|
|
- [ ] No misleading simplifications
|
|
|
|
**Issues Found**:
|
|
```
|
|
# Critical: Must fix before publication
|
|
# High: Strong recommendation to fix
|
|
# Medium: Should consider fixing
|
|
# Low: Nice to have
|
|
```
|
|
|
|
---
|
|
|
|
## 3. Style Review (文风审)
|
|
|
|
### 3.1 Audience Match
|
|
- [ ] Tone matches target audience ({{audience}})
|
|
- [ ] Jargon is appropriate or explained
|
|
- [ ] Examples resonate with readers
|
|
- [ ] Complexity level is consistent
|
|
|
|
### 3.2 Voice Consistency
|
|
- [ ] Writing style is consistent throughout
|
|
- [ ] Active voice is preferred
|
|
- [ ] Tense usage is consistent
|
|
- [ ] POV (first/second/third person) is consistent
|
|
|
|
### 3.3 Readability
|
|
- [ ] Sentences are clear and concise
|
|
- [ ] No unnecessary wordiness
|
|
- [ ] Complex ideas are well-explained
|
|
- [ ] Paragraph breaks aid scanning
|
|
|
|
**Issues Found**:
|
|
```
|
|
# Focus on patterns, not isolated issues
|
|
```
|
|
|
|
---
|
|
|
|
## 4. Format Review (格式审)
|
|
|
|
### 4.1 Markdown Compliance
|
|
- [ ] Headings use proper hierarchy (# ## ###)
|
|
- [ ] Lists are properly formatted
|
|
- [ ] Code blocks have language specified
|
|
- [ ] Links use correct syntax `[text](url)`
|
|
|
|
### 4.2 Frontmatter Integrity
|
|
- [ ] All required fields present
|
|
- [ ] Dates in ISO 8601 format
|
|
- [ ] Arrays use valid YAML syntax
|
|
- [ ] No trailing spaces or special chars
|
|
|
|
### 4.3 Asset References
|
|
- [ ] Images have alt text
|
|
- [ ] Asset paths are vault-relative
|
|
- [ ] Cover image is specified
|
|
- [ ] All referenced assets exist
|
|
|
|
**Issues Found**:
|
|
```
|
|
# Format issues block automated processing
|
|
```
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
### Issue Counts
|
|
|
|
| Category | Critical | High | Medium | Low |
|
|
|----------|----------|------|--------|-----|
|
|
| Structure | 0 | 0 | 0 | 0 |
|
|
| Factual | 0 | 0 | 0 | 0 |
|
|
| Style | 0 | 0 | 0 | 0 |
|
|
| Format | 0 | 0 | 0 | 0 |
|
|
| **Total** | **0** | **0** | **0** | **0** |
|
|
|
|
### Decision
|
|
|
|
- [ ] **PASSED** - Ready for polish (Critical=0, High≤1)
|
|
- [ ] **FAILED** - Requires revision (Critical≥1 OR High>1)
|
|
|
|
### Review Status Update
|
|
|
|
```bash
|
|
# If PASSED:
|
|
obsidian property:set path="{{path}}" name="review_status" value="passed"
|
|
obsidian property:set path="{{path}}" name="review_passed_at" value="{{iso_timestamp}}"
|
|
|
|
# If FAILED:
|
|
obsidian property:set path="{{path}}" name="review_status" value="failed"
|
|
obsidian property:set path="{{path}}" name="status" value="revision"
|
|
obsidian property:set path="{{path}}" name="revision_count" value="{{new_count}}"
|
|
```
|
|
|
|
### Reviewer Notes
|
|
|
|
> Add any additional observations or recommendations for the author.
|
|
|
|
---
|
|
|
|
## Revision Tracking
|
|
|
|
After fixes are applied:
|
|
|
|
```yaml
|
|
revision_history:
|
|
- date: "{{date}}"
|
|
issues_fixed:
|
|
- "S1: Added transition paragraph"
|
|
- "F2: Updated source URL"
|
|
notes: "Author addressed all critical issues"
|
|
```
|