rollback-revision

Roll back a change by moving a Unit head (or a set of Unit heads) to a prior revision via cub unit update --restore, then hand off to cub-apply. Use for "roll back this change", "revert the last release", "undo the ChangeSet", "restore to the last applied revision". Not for a forward one-field fix where a new cub-mutate is clearer.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, fully-actionable runbook with clear sequencing and validation for a destructive multi-shape operation. Its only real gap is progressive disclosure: four referenced files are signaled but not present in the bundle.

Suggestions

Include the referenced files under references/ (changesets.md, revisions.md, filters-and-queries.md, cub-cli.md) so the signaled one-level-deep navigation actually resolves.

If any referenced file is not essential, remove its entry from the References section to avoid pointing at missing material.

Dimension	Reasoning	Score
Conciseness	Assumes Claude knows the domain (Unit, ChangeSet, head, promote) and never pads with conceptual explanation; every section (preflight, targets, Shapes A/B/C, verify, stop conditions, tool boundary) is operational and earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready bash for each shape with real flags (--restore, --patch, --tag, --filter, --merge-source) and concrete preflight/verify commands; placeholders like <space> are standard parameterization, not pseudocode.	3 / 3
Workflow Clarity	Multi-step flows are explicitly sequenced (preflight gates 1–5, Shape B steps 1–3, verify chain 1–4) with validation checkpoints (cub unit diff to confirm head, bridgestate Ready check) and a Stop conditions feedback loop for a destructive/batch operation.	3 / 3
Progressive Disclosure	The body cleanly signals one-level-deep references (references/changesets.md, revisions.md, filters-and-queries.md, cub-cli.md) with a dedicated References section describing each, but none of those files exist in the bundle, so navigation is not actually resolvable.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tightly written description: it names the exact mechanism and command, gives multiple natural trigger phrases, states when to use it, and explicitly distinguishes it from the forward-fix alternative. Third-person voice is used throughout.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions and the exact command: 'moving a Unit head (or a set of Unit heads) to a prior revision via cub unit update --restore, then hand off to cub-apply' — no vague language.	3 / 3
Completeness	Explicitly answers both what (move head to a prior revision via cub unit update --restore, hand off to cub-apply) and when ('Use for ...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Quotes natural phrasings a user would actually say: "roll back this change", "revert the last release", "undo the ChangeSet", "restore to the last applied revision" — strong coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Clear niche (rollback via --restore) with an explicit negative trigger ('Not for a forward one-field fix where a new cub-mutate is clearer') that separates it from sibling skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	13 / 16 Passed

Repository: confighub/confighub-skills
Commit: 82d0282

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.