conductor-revert — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited conductor-revert (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Revert changes by logical work unit with full git awareness. Supports reverting entire tracks, specific phases, or individual tasks.
resources/implementation-playbook.md.conductor/tracks.md exists/conductor:setup firstgit status to confirm git repo WARNING: Uncommitted changes detected
Files with changes:
{list of files}
Options:
1. Stash changes and continue
2. Commit changes first
3. Cancel revertParse the argument format:
Full track: {trackId}
auth_20250115Specific phase: {trackId}:phase{N}
auth_20250115:phase2Specific task: {trackId}:task{X.Y}
auth_20250115:task2.3Display guided selection menu:
What would you like to revert?
Currently In Progress:
1. [~] Task 2.3 in dashboard_20250112 (most recent)
Recently Completed:
2. [x] Task 2.2 in dashboard_20250112 (1 hour ago)
3. [x] Phase 1 in dashboard_20250112 (3 hours ago)
4. [x] Full track: auth_20250115 (yesterday)
Options:
5. Enter specific reference (track:phase or track:task)
6. Cancel
Select option: git log --oneline --grep="{trackId}" --grep="Task {X.Y}" --all-match git log --oneline --grep="mark task {X.Y} complete" --grep="{trackId}" --all-match git log --oneline --grep="{trackId}" | grep -E "Task {N}\.[0-9]" git log --oneline --grep="{trackId}" git log --oneline -- "conductor/tracks/{trackId}/"Before any revert operations, display full plan:
================================================================================
REVERT EXECUTION PLAN
================================================================================
Target: {description of what's being reverted}
Commits to revert (in reverse chronological order):
1. abc1234 - feat: add chart rendering (dashboard_20250112)
2. def5678 - chore: mark task 2.3 complete (dashboard_20250112)
3. ghi9012 - feat: add data hooks (dashboard_20250112)
4. jkl3456 - chore: mark task 2.2 complete (dashboard_20250112)
Files that will be affected:
- src/components/Dashboard.tsx (modified)
- src/hooks/useData.ts (will be deleted - was created in these commits)
- conductor/tracks/dashboard_20250112/plan.md (modified)
Plan updates:
- Task 2.2: [x] -> [ ]
- Task 2.3: [~] -> [ ]
================================================================================
!! WARNING !!
================================================================================
This operation will:
- Create {N} revert commits
- Modify {M} files
- Reset {P} tasks to pending status
This CANNOT be easily undone without manual intervention.
================================================================================
Type 'YES' to proceed, or anything else to cancel:CRITICAL: Require explicit 'YES' confirmation. Do not proceed on 'y', 'yes', or enter.
Execute reverts in reverse chronological order (newest first):
Executing revert plan...
[1/4] Reverting abc1234...
git revert --no-edit abc1234
✓ Success
[2/4] Reverting def5678...
git revert --no-edit def5678~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.