docs: move edge cases section outside code block in skill-reviewer

[sjnims]

Summary

Moves the Edge Cases section outside the output format code block in skill-reviewer.md to clarify that these are operational instructions for the agent, not part of the output template.

Problem

Fixes #131

The Edge Cases section was embedded inside the output format markdown code block, creating ambiguity about whether it was example output or actual agent instructions.

Solution

Move the Edge Cases section outside the code block as a separate section, consistent with how plugin-validator.md and agent-creator.md structure their edge cases.

Alternatives Considered

• Leaving edge cases in the code block with a comment: Rejected as it still creates ambiguity
• Removing edge cases entirely: Rejected as they provide valuable operational guidance

Changes

• plugins/plugin-dev/agents/skill-reviewer.md: Close code block before Edge Cases section, move Edge Cases outside as standalone section

Testing

• Linting passes (markdownlint)
• Structure matches other agents (plugin-validator, agent-creator)

---

🤖 Generated with Claude Code

[claude]

Claude finished @sjnims's task in 58s —— View job

---

PR Review: docs: move edge cases section outside code block in skill-reviewer

Tasks

• Read the modified file
• Get PR diff to see exact changes
• Run markdownlint validation
• Review agent component structure
• Verify consistency with other agents
• Post comprehensive review

---

Summary

Looks good ✅ - This is a well-targeted documentation improvement that resolves a real ambiguity issue.

What Changed

The PR moves the Edge Cases section from inside the markdown code block to outside it as a standalone section. Specifically:

Before:

3. [Third priority]

**Edge Cases:**
- Skill with no description issues: Focus on content and organization
...

**After:**
```markdown
3. [Third priority]

Edge Cases:

• Skill with no description issues: Focus on content and organization
  ...

### What's Good

1. **Resolves Real Ambiguity**: The Edge Cases section was indeed inside the output format code block, which could mislead users into thinking these should be part of the agent's markdown output rather than operational instructions for the agent itself.

2. **Consistent with Other Agents**: I verified that both `plugin-validator.md` and `agent-creator.md` have their Edge Cases sections outside code blocks as standalone sections. This change brings `skill-reviewer.md` into alignment with that pattern.

3. **Clean Implementation**: The change is minimal and surgical - closes the code block properly at line 194 with triple backticks, adds a blank line for readability, then presents Edge Cases as a regular section.

4. **Testing Verified**: Author confirmed markdownlint passes and structure matches other agents.

### Markdown Linting
✅ **No issues found** - `markdownlint` ran successfully with no errors on the modified file.

### Checklist Verification
- ✅ Fixes the issue described in #131
- ✅ Follows the pattern used in `plugin-validator.md` and `agent-creator.md`
- ✅ Maintains proper markdown structure
- ✅ Linting passes
- ✅ No breaking changes to agent functionality

### Recommendation
**Approve and merge** - This is a straightforward documentation fix that improves clarity and consistency across agent files.

---