issue-review-reply

To draft maintainer replies for GitHub issues, this Skill translates issue reports into precise maintainer-facing interpretations, determines codebase feasibility, and generates recommended follow-up actions with explicit approval gates.

Issue review automation separates analysis from execution by enforcing explicit approval gates before performing any GitHub writes, ensuring maintainers review proposed project updates and task tracking before actions are executed.

Yes, you can track GitHub issues by proposing to add items to a GitHub Project or create tracked tasks, but the automation requires explicit maintainer approval before performing these GitHub actions.

The best way to clarify the intent and scope of a GitHub issue is to translate the user report into a concise maintainer-ready interpretation, determining feasibility against the current codebase and referencing relevant repo context.

Yes, you need to approve GitHub actions explicitly, as this workflow enforces a strict separation of analysis and execution to ensure safe, approved project updates before any writes occur.

If GitHub issue review is not capturing codebase feasibility, this Skill references relevant repo context to determine feasibility accurately, ensuring the maintainer reply and proposed task plan match current project constraints.