Skip to content

chore(skills): rewrite skill descriptions in plain language - #2701

Open
alexeyv wants to merge 2 commits into
mainfrom
chore/plain-skill-descriptions
Open

chore(skills): rewrite skill descriptions in plain language#2701
alexeyv wants to merge 2 commits into
mainfrom
chore/plain-skill-descriptions

Conversation

@alexeyv

@alexeyv alexeyv commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator

What

Rewrites the skill description layer in plain language. Descriptions carried jargon and metaphor ("SPEC kernel + companions", "lean spine of invariants", "PRFAQ gauntlet", "hardens, proves out, or dies cheaply") that bled into interactive sessions, help output, and generated artifacts, and made the catalog hard to understand.

Changes

  • SKILL.md frontmatter descriptions (16 skills across bmm and core): each rewritten in plain sentences, grounded in what the skill's body actually does — no capability is claimed that the skill does not implement.
  • module-help.csv (bmm and core): same treatment, plus restored punctuation in unquoted rows, filled the empty bmad-create-epics-and-stories description, and spelled out the CC/CR menu-code references as Correct Course / Code Review.
  • module.yaml: "Agile Ai Driven Development" → "Agile AI-driven development".
  • prfaq bmad-manifest.json: "battle-tested PRFAQ document and optional LLM distillate" → plain equivalent.

Deliberately unchanged

  • All "Use when the user says …" trigger phrases — they quote user language and drive skill discovery (including "architecture spine", since the artifact is literally named ARCHITECTURE-SPINE.md).
  • Already-plain descriptions (prd, product-brief, build-auto, brainstorming, customize, help, party-mode, advanced-elicitation, three of five agents) and all v6-shims.
  • Agent persona descriptors in module.yaml ("Speaks like a treasure hunter…") — deliberate voice design, left for a separate decision.

Validation

  • npm run validate:skills: 49 skills scanned, 0 findings.
  • Both help CSVs parse with consistent 13-column rows.
  • Full npm run quality passes.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your trial has ended. Reactivate Greptile to resume code reviews.

@coderabbitai

coderabbitai Bot commented Aug 9, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The change updates 19 skill and module descriptions. The descriptions now specify workflow actions, supported inputs, generated outputs, and review behavior. No public entity declarations change.

Changes

Skill metadata updates

Layer / File(s) Summary
Agent and module descriptions
src/bmm-skills/agents/..., src/bmm-skills/module.yaml
The analyst, developer, and BMM module descriptions now use more specific role and module wording.
Planning workflow descriptions
src/bmm-skills/plan/...
Planning descriptions now clarify architecture, PRFAQ, project context, specification, sprint planning, and UX actions and outputs.
Shipping workflow descriptions
src/bmm-skills/ship/...
Shipping descriptions now clarify implementation, review, course correction, test generation, and retrospective behavior.
Core workflow descriptions
src/core-skills/...
Core descriptions now clarify research decision support, idea testing, and review-method selection.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Suggested reviewers: bmadcode

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the primary change: rewriting skill descriptions in plain language.
Description check ✅ Passed The description directly explains the plain-language rewrites, related file updates, preserved content, and validation results.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/plain-skill-descriptions

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 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 `@src/bmm-skills/plan/bmad-project-context/SKILL.md`:
- Line 3: Restore terminal punctuation in the description at
src/bmm-skills/plan/bmad-project-context/SKILL.md:3-3 by appending a period
after “making”; apply the same punctuation-only update at
src/bmm-skills/plan/bmad-sprint-planning/SKILL.md:3-3 after “fix sprint status”
and at src/bmm-skills/plan/bmad-ux/SKILL.md:3-3 after “help me plan the UX”.

In `@src/bmm-skills/ship/bmad-code-review/SKILL.md`:
- Line 3: Add terminal periods to the descriptions on line 3 of both
src/bmm-skills/ship/bmad-code-review/SKILL.md and
src/bmm-skills/ship/bmad-qa-generate-e2e-tests/SKILL.md, placing each period
before the closing single quote.
🪄 Autofix

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 23ff39f3-a5db-4bb6-8f34-05f5de17a532

📥 Commits

Reviewing files that changed from the base of the PR and between ae7afac and b0f3199.

⛔ Files ignored due to path filters (2)
  • src/bmm-skills/module-help.csv is excluded by !**/*.csv
  • src/core-skills/module-help.csv is excluded by !**/*.csv
📒 Files selected for processing (19)
  • src/bmm-skills/agents/bmad-agent-analyst/SKILL.md
  • src/bmm-skills/agents/bmad-agent-dev/SKILL.md
  • src/bmm-skills/module.yaml
  • src/bmm-skills/plan/bmad-architecture/SKILL.md
  • src/bmm-skills/plan/bmad-prfaq/SKILL.md
  • src/bmm-skills/plan/bmad-prfaq/bmad-manifest.json
  • src/bmm-skills/plan/bmad-project-context/SKILL.md
  • src/bmm-skills/plan/bmad-spec/SKILL.md
  • src/bmm-skills/plan/bmad-sprint-planning/SKILL.md
  • src/bmm-skills/plan/bmad-ux/SKILL.md
  • src/bmm-skills/ship/bmad-build/SKILL.md
  • src/bmm-skills/ship/bmad-checkpoint-preview/SKILL.md
  • src/bmm-skills/ship/bmad-code-review/SKILL.md
  • src/bmm-skills/ship/bmad-correct-course/SKILL.md
  • src/bmm-skills/ship/bmad-qa-generate-e2e-tests/SKILL.md
  • src/bmm-skills/ship/bmad-retrospective/SKILL.md
  • src/core-skills/bmad-deep-recon/SKILL.md
  • src/core-skills/bmad-forge-idea/SKILL.md
  • src/core-skills/bmad-review/SKILL.md

---
name: bmad-project-context
description: 'Set up or refresh agent instructions so AI agents work well in it. Use when the user says "project context", "set up AGENTS.md", "document this project", "refresh context", "audit context", wants to apply coding standards or governance to a repo, or wants to record a mistake agents keep making'
description: 'Set up or refresh a repository''s agent instructions — a small verified block in AGENTS.md — so AI agents work well in that repo. Use when the user says "project context", "set up AGENTS.md", "document this project", "refresh context", "audit context", wants to apply coding standards or governance to a repo, or wants to record a mistake agents keep making'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Restore terminal punctuation in the three descriptions.

Append a period after the final activation phrase at each site.

  • src/bmm-skills/plan/bmad-project-context/SKILL.md#L3-L3: append . after making.
  • src/bmm-skills/plan/bmad-sprint-planning/SKILL.md#L3-L3: append . after "fix sprint status".
  • src/bmm-skills/plan/bmad-ux/SKILL.md#L3-L3: append . after "help me plan the UX".
📍 Affects 3 files
  • src/bmm-skills/plan/bmad-project-context/SKILL.md#L3-L3 (this comment)
  • src/bmm-skills/plan/bmad-sprint-planning/SKILL.md#L3-L3
  • src/bmm-skills/plan/bmad-ux/SKILL.md#L3-L3
🤖 Prompt for 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.

In `@src/bmm-skills/plan/bmad-project-context/SKILL.md` at line 3, Restore
terminal punctuation in the description at
src/bmm-skills/plan/bmad-project-context/SKILL.md:3-3 by appending a period
after “making”; apply the same punctuation-only update at
src/bmm-skills/plan/bmad-sprint-planning/SKILL.md:3-3 after “fix sprint status”
and at src/bmm-skills/plan/bmad-ux/SKILL.md:3-3 after “help me plan the UX”.

---
name: bmad-code-review
description: 'Adversarial code review using parallel review layers and structured triage. Use when the user says "run code review" or "review this code"'
description: 'Review code changes with several independent reviewers in parallel, then triage and present the findings. Use when the user says "run code review" or "review this code"'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add terminal punctuation to both skill descriptions.

Both descriptions end without a final period. Add the period before the closing single quote in each file.

  • src/bmm-skills/ship/bmad-code-review/SKILL.md#L3-L3: add the final period.
  • src/bmm-skills/ship/bmad-qa-generate-e2e-tests/SKILL.md#L3-L3: add the final period.
📍 Affects 2 files
  • src/bmm-skills/ship/bmad-code-review/SKILL.md#L3-L3 (this comment)
  • src/bmm-skills/ship/bmad-qa-generate-e2e-tests/SKILL.md#L3-L3
🤖 Prompt for 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.

In `@src/bmm-skills/ship/bmad-code-review/SKILL.md` at line 3, Add terminal
periods to the descriptions on line 3 of both
src/bmm-skills/ship/bmad-code-review/SKILL.md and
src/bmm-skills/ship/bmad-qa-generate-e2e-tests/SKILL.md, placing each period
before the closing single quote.

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Your trial has ended. Reactivate Greptile to resume code reviews.

Skill descriptions carried jargon and metaphor ("SPEC kernel",
"spine of invariants", "PRFAQ gauntlet", "dies cheaply") that bled
into interactive sessions, help output, and generated artifacts.

Rewrite the description layer in plain language, grounded in what
each skill's body actually does:

- SKILL.md frontmatter descriptions across bmm and core skills
- module-help.csv descriptions for bmm and core, restoring missing
  punctuation, filling the empty create-epics-and-stories entry, and
  spelling out CC/CR menu codes
- bmm module.yaml module description casing
- prfaq bmad-manifest.json capability description

"Use when the user says ..." trigger phrases are kept verbatim, and
agent persona descriptors in module.yaml are untouched.
Trailing periods on the description one-liners were inconsistent —
most SKILL.md files had them, a handful did not. Review flagged the
mismatch on the changed lines; resolve it the other way: no
description ends with a period. Internal sentence punctuation is
unchanged.
@alexeyv
alexeyv force-pushed the chore/plain-skill-descriptions branch from ee6e89e to 7d2d60b Compare August 10, 2026 10:36
@greptile-apps

greptile-apps Bot commented Aug 10, 2026

Copy link
Copy Markdown

Greptile Summary

The PR rewrites skill and catalog descriptions in clearer language without changing workflow behavior.

  • Rephrases frontmatter descriptions across BMad Method and Core skills.
  • Updates both help catalogs with clearer capability and routing summaries.
  • Clarifies module and PRFAQ manifest descriptions.
  • Preserves valid metadata and CSV structure.

Confidence Score: 5/5

The PR appears safe to merge because the metadata remains valid and the rewritten descriptions accurately reflect existing skill behavior.

The changes are limited to user-facing descriptions, preserve parser-compatible formats and discovery triggers, and introduce no accepted functional or security failures.

Important Files Changed

Filename Overview
src/bmm-skills/module-help.csv Rewrites BMad Method catalog descriptions, fills the epics-and-stories description, and preserves the valid 13-column CSV schema.
src/core-skills/module-help.csv Rephrases Core catalog entries in plain language while preserving identifiers, routing fields, and CSV structure.
src/bmm-skills/plan/bmad-spec/SKILL.md Replaces internal terminology with a plain-language description that remains consistent with the skill’s outputs and supported modes.
src/bmm-skills/plan/bmad-architecture/SKILL.md Clarifies architecture creation, update, validation, and supported inputs without changing workflow instructions.
src/core-skills/bmad-deep-recon/SKILL.md Describes the three supported research modes and built-in research types in more accessible language.
src/core-skills/bmad-review/SKILL.md Rephrases multi-lens review behavior while retaining its supported inputs, lens selection, and discovery triggers.
src/bmm-skills/module.yaml Corrects capitalization and hyphenation in the module’s user-facing description.
src/bmm-skills/plan/bmad-prfaq/bmad-manifest.json Replaces metaphorical wording with an accurate description of the PRFAQ and optional condensed output.

Reviews (1): Last reviewed commit: "style(skills): drop trailing periods fro..." | Re-trigger Greptile

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