mikaeltorni
- 15 skills
- 0 followers
- 7 hours ago last updated
- ▌ Refactoring · mikaeltorniUse when the user asks to refactor, restructure, or modularize an existing codebase. Extracts monolithic files into well-organized modules following single-responsibility principles, audits multi-repository workspaces, creates tests first (TDD), and ensures extracted code is documented, logged, and verified. Always analyze and plan module boundaries before touching code.
- ▌ Init Project · mikaeltorniUse when initializing a new project or adding Python support to existing projects. Implements anti supply-chain attack protection for Python dependencies and configures UV by Astral as the required package manager with rolling 24-hour publication delay.
- ▌ Github SEO · mikaeltorniv1.2.0 — Use when a GitHub project needs to be found: search-engine ranking, AI/LLM citability, GitHub-internal discovery, and registry presence. Runs a weighted 100-point audit, records a tracked scorecard, then closes the highest-value gap round after round until the score is a fully evidenced 100/100, and maintains it after.
- ▌ Worktree Cleanup · mikaeltorniv1.1.0 — Use when linked git worktrees have piled up and are eating disk: audit every worktree of a repository against a fixed expiry rubric, remove only the ones that are provably finished — merged, clean, unreferenced by any live agent session and by any open, in-progress, blocked or benched note — and report the round round after round until no expired worktree is left and none of the live ones was touched.
- ▌ Setup Repository Guidelines · mikaeltorniUse only when the user requests repository initialization or explicitly invokes this skill by name or tag. Missing repository guidelines, a new directory, and ordinary coding or installer work do not authorize invocation. Detects membership from scripts/repository_manifest.sh and enforces owner routing, selectable installer integration, clean-install compatibility, safe deployment, and prompt-free keyring handling.
- ▌ General Programming Guidelines · mikaeltorniv1.14.0 — Mandatory engineering workflow and coding standards for every software task: implementation, debugging, review, testing, and refactoring.
- ▌ Commit · mikaeltorniUse when the user asks to commit work that already exists in a dirty worktree: inspect the changes, split that diff into logical commits, stage hunks, and create the commits. Plan every requested repository and execute the complete commit run in the same response. Not for work this session is still authoring — the `commits` skill owns that.
- ▌ Linux Configuration · mikaeltorniMandatory rules for any task on this machine that touches Linux desktop configuration: GNOME Shell extensions, gsettings, themes, hotkeys, systemd user services, or a repository install.sh. Requires console-only, silent deployment; activates edited extension code via the sanctioned in-place X11 run-dialog reload (`xdotool` `Alt+F2 r`) and forbids destructive session restarts, logout, `gnome-shell --replace`, and shell-kill commands. Covers clean-install compatibility and the root-optional (sudo-free) installer pattern.
- ▌ Srp · mikaeltorniUse whenever writing or editing Python (or other) code: enforce single-responsibility functions and methods. Apply on every coding task, including small scripts and new files from scratch.
- ▌ Docs · mikaeltorniUse whenever writing or editing a program: after the code works, write a README.md that documents what it does, the public entrypoint, and the commands it accepts. Apply on every coding task, including small scripts and new files from scratch.
- ▌ Debug · mikaeltorniUse whenever software is reported broken or misbehaving: read the logs before forming a hypothesis. Look in repo .log/ first. Apply on every debugging task, including small scripts.
- ▌ Commits · mikaeltorniUse whenever the user prompt can be split into Features, including vague "should have X" asks: break it into one Feature per capability the prompt names, implement one at a time, and commit each Feature in the worktree while the program still works. Apply on every coding task, including small scripts and new files from scratch.
- ▌ Logging · mikaeltorniUse whenever writing or editing Python (or other) functions: print each function's incoming parameters at entry and the return value just before returning. Keep it to plain print() — no logging modules or log files.
- ▌ Worktree · mikaeltorniUse before editing a git repository: isolate work in a sibling .worktrees project group with an instance/task directory, commit there, merge into the live default branch, and reapply consumers. Applies to coding, documentation, and follow-up edits. Never push unless requested.
- ▌ Commenting · mikaeltorniUse whenever writing or editing Python (or other) functions: every function must have a docstring with a description, Parameters, and Returns in exactly that format. Apply on every coding task, including new files from scratch.