implementation_finalise
Skill21 starsChanged 3 months agoMITView on GitHub
Complete remaining unchecked tasks in the task tracker
1 other project uses a version of this.
Adopted by
Most recently taken up by
- MarcusJellinghaus/mcp-workspaceword for word, first seen Nov 14, 2026
Other versions1 project uses a version of this.
Word for word · 1
- MarcusJellinghaus/mcp-workspace★ 49100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- check_branch_statusSkill
- commit_pushSkill
- discussSkill
- implementation_approveSkill
- implementation_needs_reworkSkill
- implementation_new_tasksSkill
- implementation_reviewSkill
- implementation_review_supervisorSkill
- implement_directSkill
- issue_analyseSkill
- issue_analyse_supervisorSkill
- issue_approveSkill
- issue_createSkill
- issue_requirementsSkill
- issue_updateSkill
- plan_approveSkill
- plan_reviewSkill
- plan_review_supervisorSkill
- plan_updateSkill
- rebaseSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read pr_info/TASK_TRACKER.md and identify all unchecked tasks (- [ ]).
- Very specific: line 16
If all tasks are already checked (- [x]), report that no finalisation is needed and exit.
- Distinctive: line 24
If the task contains "commit message" (case-insensitive):
- Very specific: line 26
if the tasks before are already done, ignore this task by marking it as done [x]
- Very specific: line 30
Check pr_info/steps/ for related step files that provide context
- Distinctive: line 31
If step files don't exist, analyse based on task name and codebase
- Distinctive: line 32
Verify if the task is already complete
- Distinctive: line 33
If not complete: implement the required work
- Very specific: line 34
If complete or successfully implemented: mark as [x]
- Distinctive: line 35
If unable to complete: DO NOT mark as done - explain the issue
- Distinctive: line 39
If any code changes were made during this process:
- Distinctive: line 41
Run pylint checks using the MCP server (fix all errors)
- Distinctive: line 42
Run pytest checks using the MCP server (fix all failures)
- Distinctive: line 43
Run mypy checks using the MCP server (fix all type errors)
≈ “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
Implementation Finalise
Complete any remaining unchecked tasks in the task tracker before transitioning to code review.
Process
1. Read Task Tracker
Read pr_info/TASK_TRACKER.md and identify all unchecked tasks (- [ ]).
If all tasks are already checked (- [x]), report that no finalisation is needed and exit.
2. Process Each Unchecked Task
For each unchecked task:
Commit Message Tasks
If the task contains "commit message" (case-insensitive):
- if the tasks before are already done, ignore this task by marking it as done
[x]
Other Tasks
- Check
pr_info/steps/for related step files that provide context - If step files don't exist, analyse based on task name and codebase
- Verify if the task is already complete
- If not complete: implement the required work
- If complete or successfully implemented: mark as
[x] - If unable to complete: DO NOT mark as done - explain the issue
3. Quality Checks (If Code Changed)
If any code changes were made during this process:
- Run pylint checks using the MCP server (fix all errors)
- Run pytest checks using the MCP server (fix all failures)
- Run mypy checks using the MCP server (fix all type errors)
Output
Report:
- Which tasks were processed
- Which tasks were marked complete
- Any issues encountered
- Summarize the changes in a commit message and report it
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.

