senior-dev
Senior Dev
Act like a senior engineer mentoring the work. Improve the agent's strategy, execution discipline, and handoff quality for any coding task.
Core Rules
- HARD RULE: Keep the codebase clean, no tmp files, no dead code, no dead files. Stay organized all the time. No unnecessary folders, subfolders, or files.
- Measure twice, cut once.
- Make a task list for every task before implementation.
- Keep the task list updated as work changes.
- Prefer the smallest reversible change that solves the real problem.
- Keep folders, subfolders, and files neat, necessary, and easy to navigate.
- Remove dead code, dead files, unused files, stale temp files, and unnecessary folders only when confidence is high and verification supports it.
- Do not overcomplicate workflow, architecture, abstractions, or tooling.
- Do not overlook important facts: read relevant code, configs, docs, tests, and recent changes before editing.
- Do not claim completion without verification evidence.
Adversarial Strategy Gate
More from afu-it/safe-code
safe-code
Full repo hygiene in one pass. Uses /safe-code for first-time setup, /safe-code --continue for context-safe resume, and /safe-code --save for handoff + local commit. Detects the active agent, initializes all continuity docs inside the current project only, audits and removes dead code in safe slices, refactors in place, and keeps docs in sync. /safe-code --save creates or uses a local git repo and commits locally only — it never pushes to a remote. Universal git remote detection is informational only. Use when asked to do a full cleanup, full hygiene pass, /safe-code, or maintain a repo in one go.
9codebase-pruner
Scan an entire codebase to detect and safely remove dead code such as unused functions, orphaned modules, unreferenced exports, stale configs, dead routes, and leftover workflow artifacts. Use when asked to clean up dead code, remove unused code, prune stale files, find orphaned modules, audit codebase bloat, or delete code left behind after a workflow or architecture change.
7safe-refactor-code
Refactor code safely in small verified slices while keeping repo continuity docs in sync. Uses code-review graph tools for rename previews, impact radius, affected flows, and post-change review when available. Use when an agent is asked to refactor, restructure, clean up, remove or replace code, modernize modules, or do follow-up hygiene in a repo.
7build-graph
Build or update the code review knowledge graph. Use before safe-code audits, refactors, reviews, debugging, or when the graph may be stale.
1review-changes
Review working-tree, branch, or PR changes using graph change detection, blast-radius analysis, affected flows, and test coverage checks.
1explore-codebase
Navigate and understand codebase structure using the code-review graph. Use for repo orientation, AGENTS.md authoring, architecture mapping, or finding relevant code.
1