Skip to content

Conversation

@TabishB
Copy link
Contributor

@TabishB TabishB commented Jan 27, 2026

Summary

Adds a changeset for changes since v1.0.1.

Changes Included

  • Spec naming clarification — Updated docs, schema, and templates to clarify that specs should be named after capabilities (specs/<capability>/spec.md), not changes
  • Task checkbox format — Emphasized that tasks MUST use checkbox format (- [ ]) for apply phase tracking

PR Reference


🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Clarified naming conventions for specs: they should be organized under specs/<capability>/ directories.
    • Updated task checkbox format guidance for apply phase tracking.

✏️ Tip: You can customize this high-level summary in your review settings.

@greptile-apps
Copy link

greptile-apps bot commented Jan 27, 2026

No reviewable files after applying ignore patterns.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 27, 2026

📝 Walkthrough

Walkthrough

Adds a changelog entry documenting clarifications for the @fission-ai/openspec package. Specifies that specs should reside at specs/<capability>/spec.md and task checkboxes must use the - [ ] format for apply phase tracking.

Changes

Cohort / File(s) Summary
Changelog Entry
.changeset/spec-naming-clarification.md
New patch-level changelog entry clarifying spec naming convention and task checkbox format requirements

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

🐰 Specs now live in organized rows,
Beneath their capability homes,
Checkboxes checked with careful care,
A naming guide, neat and fair! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: adding a changeset entry for spec naming clarification, which aligns with the file modification and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@vibe-kanban-cloud
Copy link

Review Complete

Your review story is ready!

View Story

Comment !reviewfast on this PR to re-generate the story.

@TabishB TabishB merged commit e91568d into main Jan 27, 2026
9 checks passed
@TabishB TabishB deleted the changeset-spec-naming-clarification branch January 27, 2026 03:12
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.

2 participants