Repository navigation
Skills link the Jams they make: resources and relations - #25
Merged
Merged
Conversation
jam-proof, jam-fix, jam-to-e2e and jam-annotate attach the PR, ticket or CI run as a resource and mark a proof Jam as fixes/proves of the bug Jam, via jam update jam --resource/--mark-related (CLI 1.32.0) or the addResource/markRelated MCP tools.
baransu
force-pushed
the
tomasz/jam-resources-relations
branch
from
October 27, 2026 22:49
cc100da to
92e7eba
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Addresses Devin review: fixes only for a fix check that works, jam-to-ticket keeps the comment path, jam-annotate passes --type relates_to explicitly.
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.
Jam CLI 1.32.0 and the MCP server now ship resources (URLs on a Jam) and relations between Jams. The skills use them.
jam update jam --resourceand marks a fix Jam--mark-related <bug> --type fixes, orproves/relates_to. This replaces pasting the bug Jam's URL into a comment.fixesof the reported Jam. When posting on the Jam was requested, the PR goes on as a resource. CLI commands are inreferences/cli.md.fixes(bug) orproves(flow) of the source Jam, and the PR is attached.relates_to.fixesof its original Jam only when its row says works; broken or unconfirmed rows getrelates_toat most.Comment and link where it helps. Every skill that works from a Jam (jam-fix, jam-proof, jam-to-e2e, jam-to-tasks, jam-to-ticket, jam-proof-table) offers one comment on that Jam when the run settled something a viewer should know (a cause found, a fix landed, a ticket filed, a test added, a check that failed), and posts it on a yes. Inconclusive or local-only runs skip the offer. Linking happens only when there is something to link: a pull request, ticket or CI run, or a verified fix.
docs/plugin.mdand the CHANGELOG are updated.Relations from a Jam the agent created run without asking and add a "fixed by" backlink to the bug Jam. Resources on someone else's Jam ride on the yes to the comment. Every step warns against attaching URLs that carry tokens, because share pages can be public.
jam-proofandjam-annotatechanged, so the Jam CLI bundle needs a resync after merge.node scripts/check.mjspasses.