lucaspimentel

Show a sorted list of incomplete tasks from TODO.md.

Interactively walk through and address PR review comments one at a time. Accepts an optional PR number argument; defaults to the current branch's PR.

Review a pull request for issues and feedback.

Deep PR review that runs `code-review:code-review` and `pr-review-toolkit` agents in parallel, then hands off to `review-pr` for fix or post.

Use when working with Jira or Confluence from command line, including authentication, searching issues with JQL, bulk operations, sprint reports, or creating/updating work items using acli

Update project documentation based on recent changes and current codebase state.

Create or append tasks to TODO.md in the current working directory.

Commit pending changes to git. Accepts an optional argument describing what to commit (e.g. 'all changes', 'staged only', specific file names). Also accepts an optional 'push' keyword to push after committing.

Use when working with Jira or Confluence from command line, including authentication, searching issues with JQL, bulk operations, sprint reports, or creating/updating work items using acli

Pick and work on the next incomplete item from TODO.md. Use when the user says 'what's next', 'next task', 'next todo', 'what should I work on', 'what's up next', 'pick a task', 'grab something from the TODO', 'what tasks remain', 'work on the next task', 'what can I tackle next', or any variation of wanting to pick and work on the next incomplete TODO item.

Create or append tasks to TODO.md in the current working directory. Use when the user says 'add todo', 'add a task', 'TODO:', 'new task', 'track this', 'note this down', 'add to the backlog', 'before I forget', or any variation of wanting to capture new items. Also applies when the user finishes work and mentions follow-up items to save for later. Not appropriate for reading, viewing, checking off, removing, or reorganizing TODO.md.

Commit pending changes to git, optionally pushing after. Use when the user says 'commit', 'commit my changes', 'commit all', 'commit everything', 'save my work to git', 'stage and commit', or any variation of wanting to create a git commit. Accepts an optional 'push' keyword to push after committing, and optionally specific file names or a description of what to commit.

Review a pull request for issues and feedback. Use when the user says 'review this PR', 'check this PR', 'look at PR changes', 'review the diff', 'what do you think of this PR', 'post review comments', 'any issues with this PR', 'what changed in this PR', 'are there problems with these changes', 'critique the diff', or any variation of wanting PR feedback or code review.

Run one or more release actions: version, changelog, docs, commit, tag, push, watch, release. With no arguments, auto-detects needed actions from repo state and asks for confirmation. Use when the user says 'ship', 'ship it', 'ship <target>', 'version and push', 'tag and push', 'bump version and push', 'release', 'cut a release', 'publish', 'ship and watch', 'push and watch CI', 'tag and watch', or any combination of these release steps.

Manage CHANGELOG.md files and GitHub releases — add new entries, backfill missing versions, sync release notes. Use when the user says 'update changelog', 'add changelog entry', 'changelog', 'update CHANGELOG.md', 'add to changelog', 'log this change', 'update github release', 'create release notes', 'sync release notes', 'backfill changelog', 'backfill releases', 'missing changelog entries', 'create releases from tags', or any variation of wanting to add, update, backfill, or sync changelog entries or GitHub releases.

Update project documentation based on recent changes and current codebase state. Use when the user says 'update docs', 'update readme', 'sync docs', 'docs are stale', 'update CLAUDE.md', 'refresh documentation', or any variation of wanting documentation updated.

Worktrunk-specific guidance for tend CI workflows. Adds codecov polling, Rust test commands, labels, and review criteria on top of the generic tend-* skills. Use when operating in CI.

Worktrunk release workflow. Use when user asks to "do a release", "release a new version", "cut a release", or wants to publish a new version to crates.io and GitHub.

Guidance for Worktrunk (the `wt` CLI) — git worktree management, hooks, and config. Load when editing .config/wt.toml or ~/.config/worktrunk/config.toml; adding, modifying, or debugging hooks (post-merge, post-start, pre-commit, pre-merge, post-switch, etc.); configuring commit message generation or command aliases; or troubleshooting wt behavior. Also answers general worktrunk/wt questions.

CLI output formatting standards for worktrunk. Use when writing user-facing messages, error handling, progress output, hints, warnings, or working with the output system.

Run CsLint against an external codebase and analyze the results for actionable bugs (false positives, misclassifications, edge cases). Use when the user says "validate", "validate cslint", "run validation", "check for false positives", "test against", "lint and analyze", or wants to run CsLint against a target codebase to find bugs in CsLint itself. Also trigger when the user mentions analyzing lint results or finding false positives in CsLint rules.

Full-lifecycle development of TRMNL e-ink display plugins — creating new plugins, modifying existing ones, debugging template issues, and previewing locally with trmnlp. Use this skill whenever the user mentions TRMNL plugins, Liquid templates for TRMNL, e-ink display layouts, trmnlp, or wants to build/modify anything that displays on a TRMNL device. Also trigger when the user references plugin files like settings.yml, *.liquid templates, or .trmnlp.yml.