Skip to content

Share OpenSpec tooling; ignore per-developer Claude settings#61

Merged
wolfdancer merged 1 commit into
mainfrom
chore/share-openspec-tooling
Jun 17, 2026
Merged

Share OpenSpec tooling; ignore per-developer Claude settings#61
wolfdancer merged 1 commit into
mainfrom
chore/share-openspec-tooling

Conversation

@wolfdancer

Copy link
Copy Markdown
Owner

Summary

The .claude/ and openspec/ files have been sitting untracked in the repo (installed alongside the OpenSpec workflow). This tracks the shareable parts so the whole team gets the same tooling, while keeping per-developer settings out.

  • Track OpenSpec integration: .claude/commands/opsx/, .claude/skills/openspec-*/, and openspec/config.yaml.
  • Anchor secret-config ignores to the repo root (/config.yaml, /discord_config.yaml, /slack_config.yaml) so nested configs like openspec/config.yaml are no longer caught by the unanchored config.yaml rule. Root-level secret configs are still ignored.
  • Ignore .claude/settings.local.json — per-developer permission settings, not meant to be shared.

Notes

  • openspec/changes/ and openspec/specs/ are empty directories, so git doesn't track them; OpenSpec recreates them as needed.
  • Verified with git check-ignore: root secret configs + settings.local.json stay ignored; openspec/config.yaml, the *.example.yaml files, and the .claude/ tooling are trackable.

🤖 Generated with Claude Code

- Track the OpenSpec integration so the whole team gets it: .claude/commands/opsx/,
  .claude/skills/openspec-*/, and openspec/config.yaml.
- Anchor the secret-config ignore rules to the repo root (/config.yaml,
  /discord_config.yaml, /slack_config.yaml) so nested configs like
  openspec/config.yaml are no longer ignored.
- Ignore .claude/settings.local.json (per-developer permissions, not shared).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@wolfdancer wolfdancer merged commit 978cf7d into main Jun 17, 2026
1 check passed
@wolfdancer wolfdancer deleted the chore/share-openspec-tooling branch June 17, 2026 04:29
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