agentleFS
anirudhaxeanirudhaxe/friday-skills/skills/friday-5-cleanup/SKILL.md

friday-5-cleanup

Skill0 starsChanged 5 months agoMITView on GitHub

Step 5 of the Friday workflow — the final step. Remove ALL helper comments added by the Friday workflow across the entire codebase. These are any multiline comments whose first line matches 'FRIDAY-WORKFLOW'. Use only when explicitly told to execute Step 5 of the Friday workflow after all implementations are complete.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use this skill outside the Friday workflow context.

    line 15
  2. Distinctive:

    Search the codebase for all remaining FRIDAY-WORKFLOW markers:

    line 21
  3. Very specific:

    Only remove comment blocks that contain FRIDAY-WORKFLOW as their first content line

    line 49
  4. Distinctive:

    Leave all other comments in the codebase untouched

    line 50
  5. Distinctive:

    Leave all production code untouched

    line 51
  6. Distinctive:

    Do not change any logic, formatting, or actual code

    line 52
  7. Distinctive:

    After removing all comments:

    line 56
  8. Very specific:

    Run rg "FRIDAY-WORKFLOW" — should return zero results

    line 58
  9. Distinctive:

    Run any available type checker or linter to confirm code still compiles

    line 62
  10. Distinctive:

    If any markers remain, remove them and re-verify.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Friday Step 5: Cleanup — Remove FRIDAY-WORKFLOW Comments

This is the fifth and final step in the Friday workflow. After all TODOs are implemented (Step 4), strip out every comment block added by the Friday workflow, leaving only the production code behind.

When to use

  • User explicitly says "Friday step 5" or "friday-5"
  • Following a Friday workflow where Step 4 is already complete

Do not use this skill outside the Friday workflow context.

Workflow

1. Find all FRIDAY-WORKFLOW comments

Search the codebase for all remaining FRIDAY-WORKFLOW markers:

rg "FRIDAY-WORKFLOW" --include "*.{ts,tsx,js,jsx,go,py,rs,java,kt}" -n

There may be comment blocks from:

  • Step 1: FRIDAY-DATA-STRUCTURE comments (placed above data structure definitions)
  • Step 2: FRIDAY-DEFINITION comments (placed above function/component signatures)
  • Step 3: FRIDAY-TODO blocks (placed inside function bodies — these should already be removed by Step 4, but check)
  • Step 4: Any leftover markers that weren't cleaned up during implementation

2. Remove each comment block

For each match, remove the entire multiline comment block that starts with FRIDAY-WORKFLOW. The block will be a /* ... */ style comment that includes:

/*
 * FRIDAY-WORKFLOW
 * FRIDAY-{TYPE}
 * {description}
 */

Remove the entire block — not just the FRIDAY-WORKFLOW line. Do not leave empty lines where the comment was (one blank line is fine if it improves readability).

3. What NOT to remove

  • Only remove comment blocks that contain FRIDAY-WORKFLOW as their first content line
  • Leave all other comments in the codebase untouched
  • Leave all production code untouched
  • Do not change any logic, formatting, or actual code

4. Verify

After removing all comments:

  1. Run rg "FRIDAY-WORKFLOW" — should return zero results
  2. Run rg "FRIDAY-DATA-STRUCTURE" — should return zero results
  3. Run rg "FRIDAY-DEFINITION" — should return zero results
  4. Run rg "FRIDAY-TODO" — should return zero results
  5. Run any available type checker or linter to confirm code still compiles

If any markers remain, remove them and re-verify.

5. Commit consideration

The cleanup step produces a clean diff with only the implementation changes — no scaffolding comments visible. If the user wants to commit, suggest a commit message that describes the actual changes, not the workflow steps.

After completing

Report: "Cleanup complete. All FRIDAY-WORKFLOW comments removed. {N} comment blocks were cleaned across {M} files."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.