Skip to content

agents: Tighten changeset, tracker, and lint guidance - #491

Merged
QuentinRoy merged 1 commit into
mainfrom
claude/retro-d0fd5b
Oct 8, 2026
Merged

QuentinRoy merged 1 commit into
mainfrom
claude/retro-d0fd5b

Conversation

@QuentinRoy

Copy link
Copy Markdown
Owner

Summary

 AGENTS.md
-  ### Changesets: "Use /changeset when ..."
 ## Finishing
   1. pnpm build-all
+  2. Invoke /changeset
-  2. Hand off once lint, typecheck, test pass
+  3. Hand off once lint, typecheck, test pass

 docs/agents/issue-tracker.md
-  map = GitHub issue, answer = bd comment
+  map = root bead, answer = close reason
+  Asking: define internal terms on first use

 eslint.config.ts
+  ignore .claude/worktrees/**
+  no-warning-comments: 'ponytail:'
 .prettierignore, .gitignore
+  .claude/worktrees/

Evidence

  • Before: // ponytail: x in packages/runner/src passes pnpm lint. A nested agent worktree with its own eslint.config.ts crashes it with a parsing error.
    After: the same comment fails with Unexpected 'ponytail:' comment. The nested worktree is ignored. pnpm lint passes on the branch.

Merge Danger

Door: two-way

Blast Radius: agents

No package code changes, so no changeset. Anyone who writes ponytail: in a comment now gets a lint error.

Agents wrote changesets by copying older ones, so they skipped the
`/changeset` skill. The skill is now a Finishing step in `AGENTS.md`.

The tracker doc said to resolve wayfinder tickets with `bd comment` and
to keep the map in a GitHub issue. Comments cannot be edited, and maps
live in beads, so the doc now puts the answer in the close reason and
the map in the root bead. It also asks agents to define internal terms
the first time a question uses them.

`pnpm lint` now fails on `ponytail:` comments, and agent worktrees under
`.claude/worktrees/` are ignored by eslint, prettier, and git, so a
nested checkout no longer breaks lint.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Oct 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 78a69c4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@QuentinRoy
QuentinRoy enabled auto-merge (squash) October 8, 2026 14:14
@QuentinRoy
QuentinRoy merged commit f60715b into main Oct 8, 2026
6 checks passed
@QuentinRoy
QuentinRoy deleted the claude/retro-d0fd5b branch October 8, 2026 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant