chore: add changeset for profiles, Pi, Kiro, and fixes

[TabishB]

Summary

Adds a changeset covering all user-facing changes since v1.1.1:

New Features

• Profile system — core vs custom profiles with openspec config profile command
• Propose workflow — One-step change proposal creation
• AI tool auto-detection — openspec init pre-selects detected tools
• Pi (pi.dev) support — New supported coding agent
• Kiro support — New supported AWS IDE
• Sync prunes deselected workflows — openspec update cleans up removed workflows
• Config drift warning — openspec config list warns on out-of-sync config

Bug Fixes

• Fixed false "not initialized" error on fresh projects during onboard
• Fixed archive workflow stopping mid-way when syncing
• Added Windows PowerShell alternatives for onboard

Version bump: minor

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Profile system with core and custom profiles
  • One-step proposal workflow for design, specs, and tasks
  • AI tool auto-detection and pre-selection
  • Pi and Kiro coding agent support
  • Automatic cleanup for deselected workflows
  • Config sync warnings

• Bug Fixes

  • Fixed onboarding initialization errors
  • Fixed archive workflow interruption during sync
  • Added Windows PowerShell support

[greptile-apps]

No reviewable files after applying ignore patterns.

[1code-async]

Task completed.

Here's my review of PR #747:

---

PR Review: #747 — chore: add changeset for profiles, Pi, Kiro, and fixes

Overall

This is a straightforward changeset-only PR that documents user-facing changes since v1.1.1. The changeset follows the project's template structure from .changeset/README.md and correctly targets the @fission-ai/openspec package.

Feedback

1. Version bump is appropriate

The minor bump is correct here — the PR introduces multiple new features (profiles, Pi, Kiro, propose workflow, auto-detection) without breaking changes, which aligns with the version bump guide in .changeset/README.md.

2. Changeset content is well-written

The descriptions are user-facing and explain what users can now do rather than citing implementation details. This matches the "Do/Don't" guidance in the repo's changeset README. Each bullet follows the **Name** — description convention consistently.

3. Consider: one changeset vs. multiple

This is a minor process observation rather than a blocking concern. Changesets typically represent a single logical change, and this one bundles ~10 distinct features and fixes into a single file. If any of these features were introduced in separate PRs that already merged without their own changeset, bundling them retroactively like this is a reasonable approach. However, if future features are developed in their own PRs, each should ideally carry its own changeset so the changelog maps cleanly to individual contributions.

4. No code changes to verify

Since this PR only adds a .changeset/*.md file with no source code changes, there are no runtime, security, or performance implications to evaluate. The actual feature implementations were presumably landed in prior commits (the recent log shows commits for Pi support in e4c32db, profile sync in be6659c, sync pruning in a0608d0, etc.).

5. Minor suggestion: link to related PRs

For traceability, it could be helpful to reference the PRs that introduced each feature in the changeset body (e.g., (#735), (#736)). This isn't required by the project's changeset template, but it would make the eventual release notes more navigable. This is a nitpick — take it or leave it.

Verdict

This looks good to merge. The changeset is well-structured, follows project conventions, and the minor version bump is appropriate for the scope of changes described.

---

View full conversation

Powered by 1Code

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a changelog entry documenting a minor version bump for openspec, featuring new profile system configurations, propose workflow, AI tool auto-detection, Pi and Kiro agent support, sync pruning capabilities, and config drift warnings, plus bug fixes for onboarding and archive workflows.

Changes

Cohort / File(s)	Summary
Changelog Entry .changeset/profiles-pi-kiro.md	Documents minor version release with new features (profile system, propose workflow, tool auto-detection, Pi/Kiro support, sync pruning, config drift warnings) and bug fixes (onboarding preflight, archive sync, Windows PowerShell support).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: add changeset for config command and shell completions #388: Extends global configuration surface and openspec config command capabilities related to profile management.
• chore: add changeset for project config and schema commands #530: Augments project-level configuration and CLI config/schema commands with profile and config drift handling.
• chore: add changeset for OPSX experimental workflow commands #457: Touches experimental workflow/agent skills and archive/sync behavior improvements mentioned in this release.

Poem

🐰✨ Profiles pirouette, Kiro and Pi align,
Workflows propose in one sleek design,
Tools auto-detect with a hoppy sprint,
Sync prunes with care—a revision well-tint! 🌟

🚥 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 pull request title accurately describes the main change: adding a changeset that documents new features (profiles, Pi, Kiro support) and bug fixes.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-profiles-pi-kiro

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

.changeset/profiles-pi-kiro.md (1)

8-8: Expand the ff abbreviation for clarity.

ff is unexplained — changelog readers who aren't deeply familiar with the CLI won't know what command they no longer need to run.

✏️ Suggested wording

-- **Propose workflow** — New one-step workflow creates a complete change proposal with design, specs, and tasks from a single request — no need to run `new` then `ff` separately
+- **Propose workflow** — New one-step workflow creates a complete change proposal with design, specs, and tasks from a single request — no need to run `new` then `ff` (fast-forward) separately

(Or substitute whatever the full name of ff is in the project.)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.changeset/profiles-pi-kiro.md at line 8, Replace the unexplained `ff`
abbreviation in the "Propose workflow" changelog line with the full CLI command
name used in this project (e.g., "fast-forward" or the actual command), or write
it as "fast-forward (ff)" so readers understand what `ff` refers to; update the
sentence "no need to run `new` then `ff` separately" to use the expanded command
name while optionally keeping the `ff` short form in parentheses for
familiarity.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a0608d0 and 64fdaa9.

📒 Files selected for processing (1)

• .changeset/profiles-pi-kiro.md

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In @.changeset/profiles-pi-kiro.md:
- Line 8: Replace the unexplained `ff` abbreviation in the "Propose workflow"
changelog line with the full CLI command name used in this project (e.g.,
"fast-forward" or the actual command), or write it as "fast-forward (ff)" so
readers understand what `ff` refers to; update the sentence "no need to run
`new` then `ff` separately" to use the expanded command name while optionally
keeping the `ff` short form in parentheses for familiarity.