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.
In this repository7 other files it gives its agents.
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
- Distinctive: line 15
Do not use this skill outside the Friday workflow context.
- Distinctive: line 21
Search the codebase for all remaining FRIDAY-WORKFLOW markers:
- Very specific: line 49
Only remove comment blocks that contain FRIDAY-WORKFLOW as their first content line
- Distinctive: line 50
Leave all other comments in the codebase untouched
- Distinctive: line 51
Leave all production code untouched
- Distinctive: line 52
Do not change any logic, formatting, or actual code
- Distinctive: line 56
After removing all comments:
- Very specific: line 58
Run rg "FRIDAY-WORKFLOW" — should return zero results
- Distinctive: line 62
Run any available type checker or linter to confirm code still compiles
- Distinctive: line 64
If any markers remain, remove them and re-verify.
≈ “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.
Files
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}" -nThere may be comment blocks from:
- Step 1:
FRIDAY-DATA-STRUCTUREcomments (placed above data structure definitions) - Step 2:
FRIDAY-DEFINITIONcomments (placed above function/component signatures) - Step 3:
FRIDAY-TODOblocks (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-WORKFLOWas 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:
- Run
rg "FRIDAY-WORKFLOW"— should return zero results - Run
rg "FRIDAY-DATA-STRUCTURE"— should return zero results - Run
rg "FRIDAY-DEFINITION"— should return zero results - Run
rg "FRIDAY-TODO"— should return zero results - 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."
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
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.

