config: ignore the skill links that setup creates
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 95/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, git
- Domain
- tooling
Research direction
Read the template's .gitignore and add the specified skill-links block, preserving its wording and exceptions. Verify with a fresh template copy by running bun install && bun run setup && git status --short -uall; generated links should not appear. Then add .agents/skills/my-skill/SKILL.md and confirm the real skill file is untracked and can be committed.
Written by the indexing model from the issue text.
Description
Context
bun run setup (brain-kit's syncSkills, packages/core/src/lib/skills/sync.ts:1-17 in schlessera/brain-kit) materializes each package skill into .agents/skills/<name> as a relative symlink into node_modules. Its Claude emitter (packages/core/src/lib/skills/emitters/claude.ts) then links every skill into .claude/skills/<name>. Nothing in this template's .gitignore covers either directory, so /brain-init's generation commit picks up every link. That came to 55 files in a fresh walkthrough.
The maintainer ruled on schlessera/brain-kit#1097 (2026-10-07) that these links are regenerated state and stay out of a brain's history. Repo-local skills, which are real directories under .agents/skills/, stay tracked.
Scope
Add this block to the template's .gitignore, worded the same as the block brain-kit's brain doctor --fix appends (schlessera/brain-kit#1097):
# Skill links that `bun run setup` creates: package skills linked into
# .agents/skills, and every skill linked into .claude/skills. They are
# regenerated, so only real skill directories are tracked.
.agents/skills/*
!.agents/skills/*/
!.agents/skills/.gitkeep
.claude/skills/*
!.claude/skills/*/
Git treats a symlink as a file, not a directory, so the */ re-include never matches one, dangling or not, while a real skill directory is re-included. This was checked on git 2.55.
Out of scope
- What
syncSkillsmaterializes, and the emitter layout. - Existing brains, which
brain doctorcovers in schlessera/brain-kit#1097.
Acceptance criteria
- The template's
.gitignorecarries the block above, with the same wording as brain-kit'sdoctor --fixblock. - On a fresh copy of the template, after
bun install && bun run setup,git status --short -ualllists no path under.agents/skills/or.claude/skills/except a real skill directory's files and.agents/skills/.gitkeep. - A real directory added at
.agents/skills/my-skill/SKILL.mdshows as untracked, so it can be committed.
Verification
Fresh template copy: bun install && bun run setup && git status --short -uall. Then mkdir -p .agents/skills/my-skill && echo x > .agents/skills/my-skill/SKILL.md && git status --short -uall.
Contract impact
None.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from schlessera/brain-template
-
area: config priority: p2 type: feat
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
schlessera/brain-template#3 · 1 comment ·
-
agent-ready area: docs priority: p2 type: docs
Difficulty 4/5 3-5 days Newbie friendliness 50/100
schlessera/brain-template#2 · 2 comments ·
-
Generated brain depends on the Agent SDK, so brain sync finds Claude Code without a host installOpenarea: config priority: p2 type: feat
Difficulty 3/5 1-2 days Newbie friendliness 72/100
All issues in schlessera/brain-template
Similar issues
-
Flaky: mongodb-memory-server 'Port already in use' when another process starts a mongod concurrentlyOpenarea:testing bug effort:S priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
lens:agent lens:process process
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
thebristolsound/birdbrain#1772 ·
Maintainers usually reply within 1 day
-
bug priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Automattic/data-liberation-agent#685 ·
Maintainers usually reply within 1 day
-
Business
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day