issue-crafting

To write a GitHub issue with verifiable acceptance criteria, describe desired outcomes using observable behaviors rather than prescribing implementation details. This approach ensures the criteria describe what to test, making verification straightforward and avoiding narrow solution constraints.

To avoid implementation details in GitHub issues, focus on the current state and the objective. Rewrite implementation-centric wording into outcome statements that define the expected behavior, which broadens the solution space and clarifies the actual goal.

To check for duplicate GitHub issues, search both open and closed issues in the repository for similar context and objectives. This duplicate detection process prevents redundant tracking and ensures maintainers focus on unique problems.

To discover correct labels for a GitHub issue, dynamically select from the repository's existing label set based on the issue's context. This label discovery process ensures accurate categorization and improves issue tracking efficiency.

Yes, you can get milestone suggestions when drafting an issue for an internal project. If milestones are present in the repository, the issue crafting process recommends appropriate ones based on the objective and acceptance criteria provided.

To draft a clear GitHub bug report, you need to provide the context, current state, objective, and acceptance criteria. Supplying these four elements allows the issue drafting process to generate a structured body with verifiable behaviors.