Repository navigation
Make issue authoring direct and outcome-focused - #1
Merged
CheckPickerUpper merged 1 commit intoAug 3, 2026
Merged
Conversation
![jakuta-bot[bot]](https://avatars.githubusercontent.com/u/229203744?s=60&v=4){kind=small}
Contributor
Visual recap — skippedThe visual recap job did not run for this pull request. This is informational only and does not block the PR. Recap skipped for |
CheckPickerUpper
deleted the
chore/direct-github-issue-authoring-20260803
branch
August 3, 2026 20:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rewrite the to-issues skill around direct GitHub issue creation. It now requires high-level problem and outcome statements, observable acceptance criteria, evidence, duplicate checks, native relationship verification, and a publication report. It removes the issue-stream/reconciliation workflow from the skill.
Refs #2