# Revise P11 Documents from Reviewer Comments

Reviewing p11 documents with multiple collaborators creates scattered feedback that is hard to apply manually. This skill reads reviewer comments, classifies them by clarity, applies clear decisions to the source document, and publishes a new version automatically.

## Install

```bash
npx skillstore add rarexlabs/revise
```

## Metadata

- - Slug: rarexlabs-revise
- - Version: 1.0.1
- - Author: rarexlabs
- - GitHub username: rarexlabs
- - License: MIT
- - Repository: https://github.com/rarexlabs/p11-public/tree/main/plugins/p11/skills/revise
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: external\_commands
- - Quality score: 75
- - Public page: https://skillstore.pages.dev/skills/rarexlabs-revise
- - Manifest: https://skillstore.pages.dev/api/skills/rarexlabs-revise/manifest

## Capabilities

- Fetch and classify reviewer comments from p11 documents by clarity and actionability
- Apply clear reviewer decisions directly to the source document
- Publish revised document versions using the p11 CLI share command
- Flag unclear comments that need human clarification before publishing
- Reference p11 component library documentation during document editing
- Identify the target document from URLs, IDs, or conversation context

## Use Cases

- Update a Design Proposal After Team Review: A designer receives feedback on a feature proposal document. The skill applies all clear decisions from reviewer comments and publishes the updated version for final approval.
- Apply Technical Review Feedback to Documentation: An engineer collects review comments on technical documentation. The skill processes each comment, makes the requested changes, and shares the revised document.
- Batch Process Multiple Rounds of Document Review: A team lead manages iterative document reviews across multiple rounds. The skill tracks which comments were applied and which still need discussion.

## Prompt Templates

### Basic Document Revision

```
Use p11:revise to update the most recent p11 document with reviewer feedback. Fetch the comments and apply all clear decisions.
```

### Revision from a Specific Version

```
Revise p11 document at edit URL [url] from version [number]. Fetch comments from that version and apply clear decisions only.
```

### Handling Unclear or Disputed Comments

```
Use p11:revise on the current document. Classify all visible comment threads. If any need clarification, ask me how to proceed before publishing.
```

### Full Document Review with Component Reference

```
Revise the document at [url]. First read the components reference, then fetch all comments. Apply clear decisions and publish. Report which changes were made and which need my input.
```

## Limitations

- Cannot resolve comment threads that need human negotiation or clarification
- Only works with p11 documents, not other document or file formats
- Requires the p11 CLI to be installed and available in the environment
- Cannot add interactive UI components such as buttons or forms to documents

## Best Practices

- Always classify comment threads by content before making changes. Not all unresolved comments require action.
- Confirm with the user before publishing when any comment threads need human clarification.
- Read the p11 components reference before editing to ensure only supported document components are used.

## Anti Patterns

- Silently ignoring visible comment threads that need human clarification. Always ask the user how to proceed.
- Publishing revisions without first fetching and reviewing all comments on the target document.
- Adding interactive UI elements like buttons or forms to documents. Use only document-safe components from the p11 library.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-05-23T05:34:29.539\+00:00
- - Summary: All 57 static findings are false positives. Weak cryptographic algorithm flags were triggered by a hex color code \("\#2563EB" in openai.yaml:3\), a React component name \("DefinitionDescription" in components.md:34\), and YAML metadata fields \(SKILL.md:3-5\). Ruby/shell backtick execution flags were triggered by Markdown code block backticks in code fences across SKILL.md and components.md. The system reconnaissance flag on SKILL.md:92 is actually security-conscious guidance about bearer credentials. The skill has legitimate external command usage via the p11 CLI, which is expected and necessary for its document revision workflow. No malicious intent detected.

## Stats

- - Views: 0
- - Downloads: 0
- - Favorites: 0
- - Popularity score: 0