dotagents

Use when the user asks for a daily summary, standup, or wants to know what they did today — e.g. "daily summary", "standup", "what did I do today", "summary for slack", "daily update".

Use when the user says "let's discuss", "lets discuss", "I want to discuss", "can we discuss", "let's brainstorm", "lets brainstorm", "I want to brainstorm", or any variation asking to discuss/talk through/brainstorm an idea before coding — this takes priority over other requests in the same message. Also use before any creative work to discuss features, designs, or behavior changes through collaborative dialogue before writing code

Use when a plan's PR is ready to merge — marks the plan completed, checks PR status, merges to main, and syncs local main

Use when you have a written implementation plan to execute

Use when a feature or change needs an implementation plan with concrete tasks, file paths, and test steps before coding begins

Audits and optimizes GitHub profile pages — profile README, metadata fields, pinned repositories, stats widgets, and contribution visibility. Use this skill whenever the user asks to improve, create, review, or optimize their GitHub profile, or mentions "profile README", "GitHub bio", "pinned repos", "GitHub stats", "contribution graph", or "GitHub presence". Also trigger when someone says things like "make my GitHub look good", "I want a better GitHub profile", "help me stand out on GitHub", "set up my GitHub page", or "optimize my developer profile". Works for both personal profiles and organization profile pages.

Use when comparing libraries or frameworks, evaluating approaches or architectures, investigating a technology or topic, finding best practices, deep-diving into a subject, doing competitive analysis, or researching academic papers. Triggers on: "research", "compare", "evaluate", "deep-dive", "investigate", "best practices for". Not for: simple file lookups (use explore directly), quick fact checks, or tasks requiring code changes.

Use when reviewing pull requests, PRs, code changes, or code quality. Covers architecture reviews, security audits, mentoring through review feedback, and establishing review standards. Triggers on: "review", "code review", "PR review", "check this code", "audit", "security review".

Use when asked to create, write, or generate a README.md for a project. Triggers on: "create a README", "write a README", "add README", "project README".

Use when creating new skills, editing existing skills, or verifying skills work before deployment. Triggers on: "write a skill", "create a skill", "edit skill", "improve skill", "skill TDD".

Use when asking to improve a codebase, refactor for quality, find architectural issues, audit code health, or surface improvement opportunities — DRY violations, long files, weak abstractions, coupling, dead code, naming, test gaps, or inconsistent patterns.

Use when starting any new work that requires creating a git branch

Use when releasing a new version with semver bump (major/minor/patch) for any language project, before tagging and pushing

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when about to claim work is complete, before committing or creating PRs