Run any Skill in Manus with one click

$pwd:

harness-gc

Name: Harness Gc
Author: first-fluke

// Runs the harness garbage collection to clean up stale worktrees and branches. Use when user asks to "run gc", "clean up worktrees", "harness cleanup", or "gc".

Run Skill in Manus

$ git log --oneline --stat

stars:5

forks:1

updated:March 16, 2026 at 06:56

SKILL.md

readonly

name	harness-gc
description	Runs the harness garbage collection to clean up stale worktrees and branches. Use when user asks to "run gc", "clean up worktrees", "harness cleanup", or "gc".

Harness GC

When to use

User asks to run GC, garbage collection, or cleanup
Stale worktrees or branches are accumulating
Routine maintenance after a batch of issues have been completed and merged

When NOT to use

Implementing features or components — this skill only performs cleanup
Checking SPEC conformance -> use Symphony Conformance skill

Safety rules

Always run dry-run first. Never delete without showing the user what will be removed.
Never delete the main or master branch.
Never delete a worktree whose branch has an open PR.
GC follows soft-delete: flag first, delete on the next confirmed cycle. Unreferenced utilities are never auto-deleted — flag them and ask the user.

Steps

1. Show current stale worktrees (dry run)

Run the GC script in dry-run mode to list what would be cleaned without making any changes:

./scripts/harness/gc.sh --dry-run

If the script does not support --dry-run, manually inspect and list:

Worktrees whose associated PR has been merged
Branches with no commits in the last 30 days
Worktrees in done or failed status beyond config.workspace.retentionDays

Show the user the full list before proceeding.

2. Ask confirmation before deleting

Present the dry-run output to the user and ask:

The following worktrees and branches will be removed. Confirm to proceed? (yes / no)

Do not proceed if the user does not confirm. If the user says no, stop and report that no changes were made.

3. Run gc.sh

After confirmation, run the GC script:

./scripts/harness/gc.sh

GC targets per docs/harness/ENTROPY.md:

Target	Criteria	Action
Completed worktrees	PR merged, worktree still present	`git worktree remove`
Stale branches	Last commit > 30 days ago	`git branch -d` (local and remote)
Unreferenced utilities	No import references + > 30 days old	Flag only — do not delete, ask user

4. Report what was cleaned

After the script completes, report:

Harness GC Complete
===================
Worktrees removed: N
  - symphony/ACR-42
  - symphony/ACR-55

Branches deleted: N
  - symphony/ACR-42 (local + remote)
  - symphony/ACR-55 (local)

Flagged for review (not deleted):
  - src/utils/legacyParser.ts — no import references since 2024-02-01

Nothing else was changed.

If the script produced errors, report them with the full error message and suggested remediation.

References

scripts/harness/gc.sh — GC script
docs/harness/ENTROPY.md — GC targets, soft-delete policy, run schedule
docs/harness/LEGIBILITY.md — worktree lifecycle
docs/specs/workspace-manager.md — retention policy (config.workspace.retentionDays)
.github/workflows/harness-gc.yml — automated weekly GC workflow

related-skills.json

same repository

oma-backend.md

from "first-fluke/agent-valley"

Backend specialist for APIs, databases, authentication with clean architecture (Repository/Service/Router pattern). Use for API, endpoint, REST, database, server, migration, and auth work.

2026-04-215

commit.md

from "first-fluke/agent-valley"

Generate Conventional Commits spec git commits (auto-separate by feature)

2026-03-265

coordinate.md

from "first-fluke/agent-valley"

Task-based multi-agent coordination (includes Issue Remediation Loop)

2026-03-265

setup.md

from "first-fluke/agent-valley"

oh-my-agent project setup verification and configuration

2026-03-265

symphony-conformance.md

from "first-fluke/agent-valley"

Audits the current implementation for Symphony SPEC compliance and architecture rule adherence. Use when user asks to "check conformance", "audit symphony", or "verify spec compliance".

2026-03-175

symphony-component.md

from "first-fluke/agent-valley"

Implements one of the 7 Symphony components (Workflow Loader, Config Layer, Tracker Client, Orchestrator, Workspace Manager, Agent Runner, Observability). Use when user asks to "implement [component name]", "build orchestrator", or "add tracker client".

2026-03-165

package.json

"author": "first-fluke"

"repository": "first-fluke/agent-valley"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Network and Computer Systems AdministratorsComputer and Mathematical Occupations15-1244L4

name	harness-gc
description	Runs the harness garbage collection to clean up stale worktrees and branches. Use when user asks to "run gc", "clean up worktrees", "harness cleanup", or "gc".

Harness GC

When to use

User asks to run GC, garbage collection, or cleanup
Stale worktrees or branches are accumulating
Routine maintenance after a batch of issues have been completed and merged

When NOT to use

Implementing features or components — this skill only performs cleanup
Checking SPEC conformance -> use Symphony Conformance skill

Safety rules

Always run dry-run first. Never delete without showing the user what will be removed.
Never delete the main or master branch.
Never delete a worktree whose branch has an open PR.
GC follows soft-delete: flag first, delete on the next confirmed cycle. Unreferenced utilities are never auto-deleted — flag them and ask the user.

Steps

1. Show current stale worktrees (dry run)

Run the GC script in dry-run mode to list what would be cleaned without making any changes:

./scripts/harness/gc.sh --dry-run

If the script does not support --dry-run, manually inspect and list:

Worktrees whose associated PR has been merged
Branches with no commits in the last 30 days
Worktrees in done or failed status beyond config.workspace.retentionDays

Show the user the full list before proceeding.

2. Ask confirmation before deleting

Present the dry-run output to the user and ask:

The following worktrees and branches will be removed. Confirm to proceed? (yes / no)

Do not proceed if the user does not confirm. If the user says no, stop and report that no changes were made.

3. Run gc.sh

After confirmation, run the GC script:

./scripts/harness/gc.sh

GC targets per docs/harness/ENTROPY.md:

Target	Criteria	Action
Completed worktrees	PR merged, worktree still present	`git worktree remove`
Stale branches	Last commit > 30 days ago	`git branch -d` (local and remote)
Unreferenced utilities	No import references + > 30 days old	Flag only — do not delete, ask user

4. Report what was cleaned

After the script completes, report:

Harness GC Complete
===================
Worktrees removed: N
  - symphony/ACR-42
  - symphony/ACR-55

Branches deleted: N
  - symphony/ACR-42 (local + remote)
  - symphony/ACR-55 (local)

Flagged for review (not deleted):
  - src/utils/legacyParser.ts — no import references since 2024-02-01

Nothing else was changed.

If the script produced errors, report them with the full error message and suggested remediation.

References

scripts/harness/gc.sh — GC script
docs/harness/ENTROPY.md — GC targets, soft-delete policy, run schedule
docs/harness/LEGIBILITY.md — worktree lifecycle
docs/specs/workspace-manager.md — retention policy (config.workspace.retentionDays)
.github/workflows/harness-gc.yml — automated weekly GC workflow

harness-gc

Harness GC

When to use

When NOT to use

Safety rules

Steps

1. Show current stale worktrees (dry run)

2. Ask confirmation before deleting

3. Run gc.sh

4. Report what was cleaned

References

More from this repository

More from this repository

Harness GC

When to use

When NOT to use

Safety rules

Steps

1. Show current stale worktrees (dry run)

2. Ask confirmation before deleting

3. Run gc.sh

4. Report what was cleaned

References