dcr-reviewer-init

To join a deep code review round, invoke the skill with a specific task_name and suffix. This binds your reviewer identity to the active round context and ensures your feedback is traceable to the correct task.

A task_name and suffix are used in code review assignment to bind a reviewer to a specific task within an active round. The suffix uniquely identifies the reviewer, ensuring outputs are written to a dedicated reviewer artifact file.

To align code review findings with prior context, the skill reads active round artifacts like the readme and round context files. It reuses existing finding IDs where applicable to preserve continuity across review rounds.

Yes, you can write reviewer feedback to a structured artifact path. The skill outputs your findings directly to the reviewers/reviewer_<suffix>.md file, maintaining a standardized format for the current review round.

Yes, task-binding for code review requires an ongoing round. The skill is designed to join active deep code review sessions where explicit task_name and suffix parameters are necessary to establish reviewer identity and context.

A unique suffix is needed for code review output to prevent file collisions and maintain traceability. It generates a distinct reviewer_<suffix>.md artifact, ensuring your feedback is isolated and properly attributed within the round.