mass-update-issues

You can bulk update GitHub issues and sub-issues by using a command line tool that changes status, start dates, and close states simultaneously. This skill automates applying predefined logical states like 'todo', 'in-progress', and 'done' across entire issue hierarchies.

Yes, you can manage issue lifecycles in bulk by reopening closed issues or closing completed ones. This ensures your GitHub project board accurately reflects progress by applying the correct close states and status updates to parent and sub-issues.

Yes, you need the gh CLI and a configured GitHub project to update issue dates and statuses. This skill relies on the GitHub CLI to interact with your project board and execute bulk status updates and date modifications directly from the command line.

The best way to mark related tasks as done is to select the parent task and update all its sub-tasks to 'done' in one operation. This skill sets the status to 'done', manages end dates, and closes the parent issue automatically.

Yes, updating a parent GitHub issue automatically modifies all its associated sub-issues. When you change the status, dates, or close state of a parent issue, the skill cascades those specified updates down to every sub-issue on the project board.