post-ticket-review

Automating ticket review involves validating closed ticket details against project documentation, archiving validated tickets, and generating follow-up tasks. This skill uses git and YAML to interface with ticket files and maintain repository integrity.

Validating closed tickets requires checking ticket details for factual accuracy and adherence to repository guidelines. Once verified, the ticket file is automatically archived to maintain a clean and accurate project state.

Creating follow-up tickets happens during post-ticket review when new work is identified after closure. The skill automatically generates these follow-up tasks if the review process uncovers outstanding issues related to the original ticket.

Yes, you can use YAML and git to maintain repository integrity during ticket archival. The skill interfaces directly with YAML ticket files and uses git operations to ensure validated tickets are archived correctly within the repository.

The limitation of automated ticket review is its strict dependency on existing repository documentation and guidelines for factual validation. It cannot verify accuracy if project docs are missing or outdated, and it specifically targets Worldloom ticket files.