complete-github-issue

To systematically verify and resolve GitHub issues, you must first perform reconnaissance by checking existing code, git history, and linked pull requests to determine if the issue is already resolved. This prevents redundant work before any code modification begins.

Checking if a GitHub issue is already addressed requires assessing linked pull requests and git history. This reconnaissance phase identifies exactly which acceptance criteria remain unmet, ensuring high-quality issue resolution without redundant development.

Enforcing test coverage and validation when closing GitHub backlog issues requires a verification phase. You must mandate test coverage and validate acceptance criteria before closing any issue, ensuring that implementation is robust and regression-free.

Yes, you need the GitHub CLI and standard git tooling to automate issue tracking and backlog management. These tools perform the necessary reconnaissance and verify acceptance criteria before any code modification occurs.

Assessing unmet acceptance criteria for bug resolution or feature implementation involves a structured completion assessment. This process evaluates the codebase state and linked PRs to identify exactly which requirements remain unmet before proceeding.

Performing a reconnaissance phase before implementing GitHub issue requirements prevents redundant work and ensures high-quality resolution. It enforces a rigorous check of git history and codebase state to verify the issue's current status prior to code modification.