Repository navigation
feat: create a ticket from a change, or a change from a ticket - #451
Merged
danielhanold merged 8 commits intoNov 10, 2026
Merged
danielhanold merged 8 commits into
danielhanold merged 8 commits into
Conversation
- status test: an active fix change with a complete ticket is filtered out of changes by the feat type filter but its records row still carries the ticket. - docket-link-ticket link path: given only an id, the provider is tickets.provider and the URL comes from the connector's read of the ticket; with no connector, ask the person for the URL. - create path: the open operation's argv is resolved from the capability catalog, never hard-coded. Regenerated embedded assets and re-measured the two skill budget rows.
danielhanold
deleted the
feat/create-a-ticket-from-a-change-or-a-change-from-a-ticket
branch
November 10, 2026 03:16
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.
Summary
docket status --json --recordsnow reports each linked change's ticket (provider,id,url) on its records row, for active and archived changes. Thechangesrows are unchanged.docket-link-ticket, always run with the person present. Its link path is inSKILL.md, the push path (readiness check, refinement, one-approval draft, spec as proposed approach, create, attach, record after confirmation) is inreferences/create.md, and the import path is inreferences/import.md.docket-exportno longer claims ticket work in its description and points that work to the new skill.docket-link-ticketas an inline skill. Guards and budget rows cover the new files.Review
Reviewed at the
docket-review-standardtier (0 blockers, 0 important, 3 minor).recordsopenargv without saying to resolve it from the capability catalogTesting