clean-up — community clean-up, robot_sf_ll7, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Development Agents requiring automated branch validation and code formatting for Robot SF repositories. Clean up the current branch in the Robot SF repo by following docs/dev_guide.md and reusable scripts/dev commands; use when asked to tidy a branch, run Ruff format/fix, or run parallel pytest before s

ll7 ll7
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
26
Canonical Locale
en
Detected Body Locale
en

Ideal for Development Agents requiring automated branch validation and code formatting for Robot SF repositories. Clean up the current branch in the Robot SF repo by following docs/dev_guide.md and reusable scripts/dev commands; use when asked to tidy a branch, run Ruff format/fix, or run parallel pytest before s

Core Value

Empowers agents to automate branch validation by applying the dev guide workflow, running Ruff format/fix, and executing parallel tests, ensuring consistency and accuracy in Robot SF repositories using Ruff and parallel testing protocols.

Ideal Agent Persona

Ideal for Development Agents requiring automated branch validation and code formatting for Robot SF repositories.

↓ Capabilities Granted for clean-up

Automating branch validation for Robot SF repositories
Running Ruff format/fix for code consistency
Executing parallel tests for efficient validation

! Prerequisites & Limits

  • Requires Robot SF repository structure
  • Dependent on Ruff format/fix and parallel testing tools
  • Limited to validating branches according to the dev guide workflow

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is clean-up?

Ideal for Development Agents requiring automated branch validation and code formatting for Robot SF repositories. Clean up the current branch in the Robot SF repo by following docs/dev_guide.md and reusable scripts/dev commands; use when asked to tidy a branch, run Ruff format/fix, or run parallel pytest before s

How do I install clean-up?

Run the command: npx killer-skills add ll7/robot_sf_ll7/clean-up. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for clean-up?

Key use cases include: Automating branch validation for Robot SF repositories, Running Ruff format/fix for code consistency, Executing parallel tests for efficient validation.

Which IDEs are compatible with clean-up?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for clean-up?

Requires Robot SF repository structure. Dependent on Ruff format/fix and parallel testing tools. Limited to validating branches according to the dev guide workflow.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ll7/robot_sf_ll7/clean-up. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use clean-up immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

clean-up

Install clean-up, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Clean Up

Overview

Clean and validate the current branch for the Robot SF repo by applying the dev guide workflow, running Ruff format/fix, and running parallel tests.

Cleanup Workflow

  1. Confirm repo and guidance

    • Verify the working directory looks like the Robot SF repo (e.g., .git, docs/dev_guide.md, .specify/memory/constitution.md, and .github/copilot-instructions.md exist).
    • Read docs/dev_guide.md, .specify/memory/constitution.md, and .github/copilot-instructions.md to align with required rules.

  2. Ensure environment

    • If VIRTUAL_ENV is empty and .venv/bin/activate exists, run source .venv/bin/activate.
    • If .venv/bin/activate is missing, follow dev guide setup: uv sync --all-extras, source .venv/bin/activate, and uv run pre-commit install.

  3. Run formatting and fixes first

    • Use the shared script: scripts/dev/ruff_fix_format.sh
    • If Ruff reports issues, fix them and rerun until clean.

  4. Run tests in parallel

    • Use the shared script: scripts/dev/run_tests_parallel.sh
    • Default behavior is fail-fast + failed-first ordering: pytest -n auto -x --failed-first
    • Optional ordering toggle: scripts/dev/run_tests_parallel.sh --new-first
    • To disable fail-fast when you need a full failure set: scripts/dev/run_tests_parallel.sh --no-fast-fail
    • If tests fail, evaluate test value first (Constitution Principle XIII / dev guide testing strategy). Classify failures and decide whether to fix, defer, or ask for direction before removing or relaxing tests.

  5. Run diff-based quality gates and fix them.

    • Run changed-files coverage check: BASE_REF=origin/main scripts/dev/check_changed_coverage.sh
      • If you changed any test files, run these new tests locally.
    • Run touched-definition TODO docstring check: BASE_REF=origin/main scripts/dev/check_docstring_todos_diff.sh

  6. Report and follow-ups

    • Summarize commands run and results.
    • Note remaining failures, flaky tests, or follow-up tasks (for example, GUI tests if rendering changes were made, or CHANGELOG updates for user-facing changes).
  • Suggest commit batches and messages for any uncommited changes.

Related Skills

Looking for an alternative to clean-up or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer