Skip to content

feat(mutils): conditional-normative-notation スキルを追加#70

Merged
masseater merged 1 commit into
masterfrom
worktree-conditional-normative-notation-skill
May 27, 2026
Merged

feat(mutils): conditional-normative-notation スキルを追加#70
masseater merged 1 commit into
masterfrom
worktree-conditional-normative-notation-skill

Conversation

@masseater
Copy link
Copy Markdown
Owner

@masseater masseater commented May 27, 2026

概要

mutils プラグインに mutils:conditional-normative-notation スキルを追加する。

エージェント向けの規約(AGENTS.md / CLAUDE.md / .claude/rules/**)を 曖昧さなく 書くための記法ガイド。散文の指示を次の2層に分解して記述する手順・例・チェックリストを提供する。

  • 要求度キーワード層 — RFC 2119(MUST / MUST NOT / SHOULD / SHOULD NOT / MAY)
  • 条件付きルール構造層IF: <条件>; THEN <キーワード>: <行動> のプロダクションルール

このリポジトリのルート AGENTS.md が既に採用しているこの記法を、再利用可能なスキルとして明文化したもの。

変更内容

  • plugins/mutils/skills/conditional-normative-notation/SKILL.md(新規)
  • plugins/mutils/AGENTS.md — component-list 自動生成テーブルの再生成(bun run docs
  • plugins/mutils/plugin.json / .claude-plugin/marketplace.json — version bump(0.20.0 → 0.21.0、repository-lint/require-version-bump ルール準拠)

検証

  • bun run check(eslint + oxfmt + turbo check): green
  • bun run check:docs / bun run check:plugin-list: green
  • bun run test: green(94 tests)
  • pre-push フック(build / typecheck / check / check:lockfile / test / knip): green

関連 Issue

関連 Issue を検索したが、本スキルに対応する open Issue は存在しなかった(open は Dependency Dashboard のみ)。

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features

    • Introduced Conditional Normative Notation skill for writing unambiguous project agreements readable by agents, featuring enforcement keywords, conditional logic structures, priority handling, and quality validation guidelines.
  • Chores

    • Bumped mutils plugin version to 0.21.0.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 27, 2026

Warning

Review limit reached

@masseater, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 20 minutes and 43 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 01bf1c2c-b57d-4c69-b8b0-7ab458892733

📥 Commits

Reviewing files that changed from the base of the PR and between fa64bcc and 5b71d5e.

📒 Files selected for processing (4)
  • .claude-plugin/marketplace.json
  • plugins/mutils/AGENTS.md
  • plugins/mutils/plugin.json
  • plugins/mutils/skills/conditional-normative-notation/SKILL.md
📝 Walkthrough

Walkthrough

This PR releases mutils plugin version 0.21.0, introducing a new "Conditional Normative Notation" skill for expressing agent-readable project agreements. Version manifests are synchronized, the new skill is registered in the component list, and comprehensive skill documentation is provided defining RFC 2119–based conditional structures and validation patterns.

Changes

mutils 0.21.0 Release with Conditional Normative Notation Skill

Layer / File(s) Summary
Version and manifest updates
plugins/mutils/plugin.json, .claude-plugin/marketplace.json
Plugin version fields bumped from 0.20.0 to 0.21.0 across both the local plugin manifest and marketplace registry.
Skill component registration
plugins/mutils/AGENTS.md
Auto-generated component list table updated to add the new mutils:conditional-normative-notation skill entry.
Conditional Normative Notation skill guide
plugins/mutils/skills/conditional-normative-notation/SKILL.md
New documentation introduces a two-layer conditional normative notation system separating RFC 2119 enforcement keywords (MUST, MUST NOT, SHOULD, SHOULD NOT, MAY) from applicability conditions using IF: <condition>; THEN <keyword>: <action> structures, with guidance on condition composition, prioritization, and prose-to-rule conversion patterns.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A new skill hops into view,
With rules and conditions crystal-true,
IF this, THEN that—no ambiguity!
Version bumped, the release takes flight,
Agent agreements, now written right!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly describes the main change: adding the conditional-normative-notation skill to the mutils plugin, which aligns with the primary objective and all changes in the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch worktree-conditional-normative-notation-skill

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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@plugins/mutils/skills/conditional-normative-notation/SKILL.md`:
- Line 12: The SKILL.md currently contains a bare `$ARGUMENTS` placeholder with
no explanation; update the document to either (1) document the expected runtime
arguments and format under an `argument-hint` or `Arguments` section—describe
names, types, optional/required, and parsing/rules consistent with other
SKILL.md files—or (2) remove the `$ARGUMENTS` line if this skill accepts no
runtime arguments; ensure you reference the `$ARGUMENTS` placeholder in the
change and mirror the same convention used by other skills for clarity.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8c01487c-d58d-47f1-8ca1-0806adf98ecb

📥 Commits

Reviewing files that changed from the base of the PR and between f73feb3 and fa64bcc.

📒 Files selected for processing (4)
  • .claude-plugin/marketplace.json
  • plugins/mutils/AGENTS.md
  • plugins/mutils/plugin.json
  • plugins/mutils/skills/conditional-normative-notation/SKILL.md

Comment thread plugins/mutils/skills/conditional-normative-notation/SKILL.md Outdated
@masseater masseater force-pushed the worktree-conditional-normative-notation-skill branch from fa64bcc to f85ca3d Compare May 27, 2026 06:56
AGENTS.md / CLAUDE.md / .claude/rules を RFC 2119 キーワードと
IF/THEN 形式のプロダクションルールで書くための記法ガイド。
散文の指示を強制力層と条件構造層の2層に分解し、エージェントが
一意に解釈できる規範へ変換する手順・例・チェックリストを提供する。

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@masseater masseater force-pushed the worktree-conditional-normative-notation-skill branch from f85ca3d to 5b71d5e Compare May 27, 2026 07:28
@masseater masseater enabled auto-merge (squash) May 27, 2026 07:29
@masseater masseater merged commit 95aaae8 into master May 27, 2026
6 checks passed
@masseater masseater deleted the worktree-conditional-normative-notation-skill branch May 27, 2026 07:29
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.

1 participant