Skip to content

feat(me): add user-invocable to commit-push-pr skill - #6

Merged
baleen37 merged 1 commit into
mainfrom
wip/add-user-invocable-to-commit-push-pr-skill
Jan 14, 2026
Merged

feat(me): add user-invocable to commit-push-pr skill#6
baleen37 merged 1 commit into
mainfrom
wip/add-user-invocable-to-commit-push-pr-skill

Conversation

@baleen37

@baleen37 baleen37 commented Jan 12, 2026

Copy link
Copy Markdown
Owner

Summary

  • Added user-invocable: true to commit-push-pr skill frontmatter
  • Enables skill invocation as slash command in Claude Code 2.1.0+

Test plan

  • Follows Conventional Commits format
  • Pre-commit hooks passed
  • Commitlint validation passed

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com

Summary by CodeRabbit

  • New Features
    • The commit-push-pr skill is now user-invocable, enabling users to directly access and execute this functionality.

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

Allow commit-push-pr skill to be invoked as a slash command.
Added user-invocable: true to frontmatter for Claude Code 2.1.0+.

Co-Authored-By: Claude <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jan 12, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

A metadata flag user-invocable: true was added to the YAML header of the commit-push-pr skill manifest, enabling user invocation of this skill without any functional logic modifications.

Changes

Cohort / File(s) Summary
Skill Metadata
plugins/me/skills/commit-push-pr/SKILL.md
Added user-invocable: true property to skill manifest metadata declaration

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A skill now opens its door so wide,
With user-invocable set with pride,
No logic changed, just a flag unfurled,
Inviting users to use this world! ✨

🚥 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 reflects the main change: adding the user-invocable flag to the commit-push-pr skill metadata.
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.


📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4c5e661 and e4c7c4b.

📒 Files selected for processing (1)
  • plugins/me/skills/commit-push-pr/SKILL.md
🧰 Additional context used
📓 Path-based instructions (1)
plugins/*/skills/**/SKILL.md

📄 CodeRabbit inference engine (CLAUDE.md)

All skills must be placed in skills/*/SKILL.md with context-aware guidelines and domain best practices

Files:

  • plugins/me/skills/commit-push-pr/SKILL.md
🔇 Additional comments (2)
plugins/me/skills/commit-push-pr/SKILL.md (2)

1-5: Verify path structure compliance with coding guidelines.

The file is located at plugins/me/skills/commit-push-pr/SKILL.md, but the coding guideline states: "All skills must be placed in skills/*/SKILL.md". This path pattern appears inconsistent.

Please confirm whether the current path structure is intentional or if the file should be relocated to match the guideline pattern.

As per coding guidelines, the expected path pattern is skills/*/SKILL.md.


4-4: The user-invocable: true property is correct and properly formatted.

The property name, boolean syntax, and placement in YAML frontmatter match Claude Code 2.1.0+ documentation. When set to true, it enables slash-command invocation for the skill. This property is optional—other skills in the codebase omit it (defaulting to model-invoked only), while this skill explicitly enables user invocation.


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.

@baleen37
baleen37 merged commit e48043e into main Jan 14, 2026
3 checks passed
github-actions Bot added a commit that referenced this pull request Jan 14, 2026
# [1.3.0](v1.2.0...v1.3.0) (2026-01-14)

### Features

* **me:** add user-invocable to commit-push-pr skill frontmatter ([#6](#6)) ([e48043e](e48043e))
@github-actions

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.3.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

baleen37 added a commit that referenced this pull request Jan 31, 2026
…is missing

The update-checker.sh script was exiting early when MARKETPLACE_FILE
was not set or didn't exist, without creating the last-check timestamp
file. This caused test #6 to fail in CI.

The fix moves the timestamp update before the marketplace check, so the
timestamp is always created (unless --check-only is used), regardless of
whether a marketplace file exists.

Co-Authored-By: Claude <noreply@anthropic.com>
baleen37 added a commit that referenced this pull request Jan 31, 2026
* fix(ci): test release workflow fix

Add debug logging to semantic-release step to troubleshoot
release workflow issues. This test commit will verify the
fix works correctly.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(auto-updater): ensure timestamp is created even when marketplace is missing

The update-checker.sh script was exiting early when MARKETPLACE_FILE
was not set or didn't exist, without creating the last-check timestamp
file. This caused test #6 to fail in CI.

The fix moves the timestamp update before the marketplace check, so the
timestamp is always created (unless --check-only is used), regardless of
whether a marketplace file exists.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
baleen37 added a commit that referenced this pull request Jan 31, 2026
Added debug output to verify CONFIG_DIR and timestamp file
creation in CI environment.

Co-Authored-By: Claude <noreply@anthropic.com>
baleen37 added a commit that referenced this pull request Jan 31, 2026
* chore: trigger new release with auto-updater fix

This empty commit triggers a new release to properly include
the auto-updater fix from the previous release.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(auto-updater): add enhanced debug logging for timestamp creation

Added verification after timestamp creation to detect race conditions
or environment-specific issues in CI.

Co-Authored-By: Claude <noreply@anthropic.com>

* test(auto-updater): add debug logging to test #6

Added debug output to verify CONFIG_DIR and timestamp file
creation in CI environment.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
baleen37 added a commit that referenced this pull request Jan 31, 2026
Changed TEMP_DIR from using $$ (PID) to $BATS_TEST_NAME to ensure
each test has its own isolated temp directory. This fixes test #6
failing in CI due to shared state between tests.

Root cause: When BATS runs tests in the same process, $$ returns
the same PID for all tests, causing them to share the same TEMP_DIR.
This leads to race conditions where one test's teardown affects
another test's state.

Co-Authored-By: Claude <noreply@anthropic.com>
baleen37 added a commit that referenced this pull request Jan 31, 2026
Changed TEMP_DIR from using $$ (PID) to $BATS_TEST_NAME to ensure
each test has its own isolated temp directory. This fixes test #6
failing in CI due to shared state between tests.

Root cause: When BATS runs tests in the same process, $$ returns
the same PID for all tests, causing them to share the same TEMP_DIR.
This leads to race conditions where one test's teardown affects
another test's state.

Co-Authored-By: Claude <noreply@anthropic.com>
baleen37 added a commit that referenced this pull request Jan 31, 2026
* chore: trigger new release with auto-updater fix

This empty commit triggers a new release to properly include
the auto-updater fix from the previous release.

Co-Authored-By: Claude <noreply@anthropic.com>

* fix(auto-updater): use unique temp directory per test

Changed TEMP_DIR from using $$ (PID) to $BATS_TEST_NAME to ensure
each test has its own isolated temp directory. This fixes test #6
failing in CI due to shared state between tests.

Root cause: When BATS runs tests in the same process, $$ returns
the same PID for all tests, causing them to share the same TEMP_DIR.
This leads to race conditions where one test's teardown affects
another test's state.

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant