Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: specify init writes speckit.manifest.json without the speckit-converge skill it just installed

Open Beginner friendly
#4,273 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
cli, tooling

Research direction

Reproduce with specify init --here --integration claude --force using spec-kit v1.0.1, then compare .specify/integrations/speckit.manifest.json with the installed .claude/skills/speckit-converge/SKILL.md and the other listed speckit-* files. Trace the init manifest generation path and verify that the generated manifest includes every skill file installed by the command, including converge.

Written by the indexing model from the issue text.

Description

bug-assess severity-medium

Version

spec-kit v1.0.1, specify init --here --integration claude --force

Description

After an in-place upgrade, .specify/integrations/speckit.manifest.json lists 9 speckit-* SKILL.md entries under files — but init also installed .claude/skills/speckit-converge/SKILL.md, which is absent from the manifest.

Any tooling that uses the manifest to classify vendored files (pristine / modified / missing / untracked — e.g. deciding whether the next specify init will clobber local work) sees converge as untracked: it cannot be classified at all, which is the worst of the four states for a file the installer itself owns.

Observed identically on two independent upgrades (a template repo and a workflows repo, both 0.5.0 → v1.0.1 in-place).

Expected behavior

The generated manifest includes every skill file the init run installs, converge included.

Dominant language
Python
Stars
138k
Forks
12.4k
Avg merge
3d 6h
Merged PRs (30d)
145

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/spec-kit

All issues in github/spec-kit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.