Repository navigation
feat: follow a companion skill when creating a ticket - #455
Merged
danielhanold merged 3 commits intoNov 11, 2026
Merged
danielhanold merged 3 commits into
danielhanold merged 3 commits into
Conversation
danielhanold
deleted the
feat/follow-the-team-s-own-ticket-skill-for-project-specific-tick
branch
November 11, 2026 02:13
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
When
docket-link-ticketcreates a ticket from a change, it now finds the person's companion skill (their team's own ticket skill) and follows it for project-specific details: title format, ticket type when the skill states one, sprint and custom fields, labels, after-creation actions, and call pacing. Docket still owns the readiness check, the description body, the approved draft (which now shows everything the companion skill will do), and recording the link only after the connector confirms.tickets.companion_skill, settable at any config layer with normal precedence (unlike the repository-onlytickets.*siblings), documented indocs/reference/config-keys.mdand.docket.example.yml.create.mdgains a step 4: read the key, warn in one line and fall back to description matching when the named skill is missing, ask when several match, behave as before when none match.change_0591_companion_skillcontract pins the new text and forbids the old wording.Review
Reviewed by
docket-review-standardover the whole branch: no findings.Testing
Full suite green at the PR head. New
TestTicketsCompanionSkillAnyLayerplus the alignment contract, both mutation-tested. A live check against a real ticket system from another repository is listed as an Important human action in the results.