review-brand
Internal brand & copy review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks changed user-facing copy against the project's brand doc: voice, terminology, and honesty of claims — applies only to surfaces wit
Install
npx skills add https://github.com/gtrabanco/agentic-workflow/tree/main/skills/review-brand
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install gtrabanco-agentic-workflow@llmmart
git clone https://github.com/gtrabanco/agentic-workflow.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole gtrabanco/agentic-workflow collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Review Brand & Copy (internal)
Composed by review-change / product-audit within their conversation — on any
agent, follow this file inline as the routed step. Findings only; never edits,
never refactors.
Scope
The diff or path/glob the caller passes; default the current change vs the default branch. State the scope at the top of the returned table.
Checklist (evaluate EVERY item — none is optional; n/a must be stated)
- ✓ Read the project's brand doc first (e.g.
docs/brand/BRAND.md) — cite the rule for every finding; n/a all items if the project has none and say so - ✓ Tone of changed copy matches the declared voice (cite the guideline violated)
- ✓ Product/domain terms used consistently with the declared glossary (same concept, same word, same capitalization)
- ✓ No forbidden/deprecated phrases from the brand doc
- ✓ Claims are honest: limits, restrictions, and reductions the code enforces
are disclosed in the copy (an undisclosed limitation is a
WARNINGfinding — repo hard rule) - ✓ Error/empty-state copy is actionable (says what happened and what to do), not blame-y
- ✓ Consistency across the changed surface and its siblings (same action labeled the same way everywhere)
- ✓ Placeholder/lorem text absent from the diff
Materiality bar
Report a row only when a competent user's outcome changes or a rule the project
explicitly declares is violated — cite the rule it violates beside the evidence.
Not findings: comment/punctuation typos, formatting-only drift, style preference
with no cited rule, hypothetical robustness beyond the SPEC's named scenarios.
An empty table with Decision: PASS is the expected result for a well-formed
change — never pad the table.
Return exactly
Sev and Impact are the two published closed sets (BLOCKER | CRITICAL | WARNING | SUGGESTION and blocking | docs-only | report-only); their meanings
are owned by review-implementation (CLASSIFY.md §Severity ladder) — assign a
token, never a prose grade.
REVIEW BRAND — scope: <scope>
| # | Finding | Sev | Impact | Evidence | Suggested fix |
|---|---------|-----|--------|----------|---------------|
| 1 | <what> | BLOCKER|CRITICAL|WARNING|SUGGESTION | blocking|docs-only|report-only | <file:line> | <smallest action> |
Checklist: <n> evaluated, <n> pass, <n> findings, <n> n/a (<which + why>)
Summary: <1-2 sentences>
Decision: PASS | FAIL
FAIL if any BLOCKER, CRITICAL or WARNING finding is open; PASS otherwise.
SUGGESTION findings never block — they route to the caller's triage step.
Done when
- Every checklist item was evaluated with evidence (file:line or command output) or explicitly marked n/a with the reason.
- The fixed-format block above is returned — nothing more, nothing less — and no code was changed.
Files (agentic-workflow)
-
SKILL.md 3.3 KB
--- name: review-brand user-invocable: false version: 4.10.0 author: "Gabriel Trabanco <1969593+gtrabanco@users.noreply.github.com>" license: MIT description: > Internal brand & copy review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks changed user-facing copy against the project's brand doc: voice, terminology, and honesty of claims — applies only to surfaces with user-facing text. Findings only; never edits code. --- # Review Brand & Copy (internal) Composed by `review-change` / `product-audit` within their conversation — on any agent, follow this file inline as the routed step. **Findings only; never edits, never refactors.** ## Scope The diff or path/glob the caller passes; default the current change vs the default branch. State the scope at the top of the returned table. ## Checklist (evaluate EVERY item — none is optional; n/a must be stated) - ✓ Read the project's brand doc first (e.g. `docs/brand/BRAND.md`) — cite the rule for every finding; n/a all items if the project has none and say so - ✓ Tone of changed copy matches the declared voice (cite the guideline violated) - ✓ Product/domain terms used consistently with the declared glossary (same concept, same word, same capitalization) - ✓ No forbidden/deprecated phrases from the brand doc - ✓ Claims are honest: limits, restrictions, and reductions the code enforces are disclosed in the copy (an undisclosed limitation is a `WARNING` finding — repo hard rule) - ✓ Error/empty-state copy is actionable (says what happened and what to do), not blame-y - ✓ Consistency across the changed surface and its siblings (same action labeled the same way everywhere) - ✓ Placeholder/lorem text absent from the diff ## Materiality bar Report a row only when a competent user's outcome changes or a rule the project explicitly declares is violated — cite the rule it violates beside the evidence. Not findings: comment/punctuation typos, formatting-only drift, style preference with no cited rule, hypothetical robustness beyond the SPEC's named scenarios. An empty table with `Decision: PASS` is the expected result for a well-formed change — never pad the table. ## Return exactly `Sev` and `Impact` are the two published closed sets (`BLOCKER | CRITICAL | WARNING | SUGGESTION` and `blocking | docs-only | report-only`); their meanings are owned by `review-implementation` (`CLASSIFY.md` §Severity ladder) — assign a token, never a prose grade. ``` REVIEW BRAND — scope: <scope> | # | Finding | Sev | Impact | Evidence | Suggested fix | |---|---------|-----|--------|----------|---------------| | 1 | <what> | BLOCKER|CRITICAL|WARNING|SUGGESTION | blocking|docs-only|report-only | <file:line> | <smallest action> | Checklist: <n> evaluated, <n> pass, <n> findings, <n> n/a (<which + why>) Summary: <1-2 sentences> Decision: PASS | FAIL ``` FAIL if any `BLOCKER`, `CRITICAL` or `WARNING` finding is open; PASS otherwise. `SUGGESTION` findings never block — they route to the caller's triage step. ## Done when - Every checklist item was evaluated with evidence (file:line or command output) or explicitly marked n/a with the reason. - The fixed-format block above is returned — nothing more, nothing less — and no code was changed.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.