SrdjanCoric
UserMy personal Claude Code skills
Categories
Indexed Skills (21)
map-it-out
Manually map and resolve a large, uncertain initiative as local decision records, dependencies, frontier, fog, scope, and planning clusters, releasing each resolved decision or completed cluster for planning as soon as it is ready. Use only through explicit start, resume, status, or release commands.
software-repository-guidelines
Manually assess a repository's engineering health against a practical checklist and return evidence-backed, prioritized hardening recommendations. Invoke explicitly for a repository audit, setup, or hardening initiative; it never runs automatically during planning, implementation, testing, review, or PR work.
code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
create-pr
Open or update a pull request and handle in-scope CI failures. Use when the user wants to prepare a PR. For matching managed tasks, finalize the task as ready to merge; stop only when the current head is CI-green, and never merge or invoke sync-main.
design-it-twice
Produce and compare divergent designs for a consequential, hard-to-reverse software interface or seam using isolated parallel design subagents. Use from talk-it-through only after constraints and factual unknowns are known, or standalone when first-solution anchoring would be costly.
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Build a feedback loop → reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, describes a performance regression, or hands you an issue summary from a previous session.
finish-task
Finish an implemented and reviewed task — README audit, final behavior proof, completion record, PR creation after approval, and cleanup of the task's retained review files after CI passes. Use manually after the task-review and review-fix-worker loop is clean. Lightweight orchestration suited to a small fast model.
handoff
Capture a focused slice of the current work — a bug, a newly-discovered piece of work, or some other context — into a handoff document a fresh agent can pick up and continue without re-deriving everything. Requires an argument naming what the handoff is about.
implement-next-task
Select, claim, and set up the next eligible local task, then implement it through tdd-worker with TDD and focused validation while minimizing parent-context growth and avoidable wall time. Stops before review; the user then runs task-review, review-fix-worker, and finish-task manually.
research-for-planning
Resolve factual questions that block software planning through isolated authoritative research, then save one compact Markdown artifact with claim-level citations, applicability, and unresolved uncertainty. Use from talk-it-through or standalone when external facts—not user decisions—constrain a plan.
review-fix-worker
Fix open findings from a reviews/ todo-list file one by one with TDD, checking each off in the file. Starts from a fresh context using only the self-contained review file. Handles skip decisions for minor findings and user decisions for security findings. Use manually after task-review.
sync-main
Merge a verified pull request remotely, synchronize local main, clean verified merged branches, and move the matching local task to done. Use when the user explicitly asks to merge a ready PR, sync main, return to main, or close a merged task.
talk-it-through
Adaptively resolve a software planning question through repository inspection, focused human discussion, authoritative research, and divergent interface design when consequential. Use standalone for bounded planning or as the stateless decision-resolution engine called by map-it-out.
task-review
Review a completed task branch with one independent parallel review panel and write a self-contained findings todo-list under reviews/. Retains every review pass until finish-task removes the task's review files. Never remediates; the user runs review-fix-worker for fixes. Use standalone after implement-next-task.
tdd-worker
Implement a claimed task's work items with the cost-aware TDD red-green-refactor loop and focused tier validation. Invoked by implement-next-task with a reconnaissance digest, or standalone with a task-file path when the branch and classification already exist.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
teach
Teach the user a new skill or concept in a persistent teaching workspace. Use whenever the user says "teach me", asks to be taught something, or asks to learn or study a topic.
to-plan
Turn a PRD, decision document, or conversation into the smallest independently verifiable vertical tasks under plans/tasks/, append them to the project's single local master plan, and wait for user approval before writing. Use to plan features, tracer-bullet work, or agreed decisions for implement-next-task.
write-a-prd
Convert a plan-ready planning brief or completed conversation into a durable PRD while preserving behavioral scenarios, implementation decisions, testing seams, acceptance proof, research evidence, non-goals, and unresolved checkpoints. Use after talk-it-through when a product-facing PRD is useful before to-plan.
write-planning-brief
Distill a completed planning discussion and its cited evidence into a durable, plan-ready local brief without reopening the interview. Use at the end of talk-it-through or when a conversation must become reliable input for write-a-prd or to-plan.
write-well
Write and revise prose in a direct, human, anti-AI voice when another workflow explicitly invokes this skill.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.