all publishers

driangle

@driangle source repo

54 published skills

  1. ▌
    Release 2 · driangle bundle
    Create a new release by bumping versions, tagging, pushing, and generating release notes. Use when the user wants to release a new version.
    77 repo stars
  2. ▌
    Audit Docs 2 · driangle
    Audit documentation coverage for a project: discover CLI commands, public APIs, configuration options, and features, then cross-reference against documentation to find gaps, stale content, and missing sections. Use when the user wants to check if docs are up to date, find undocumented features, or verify doc completeness.
    77 repo stars
  3. ▌
    Do Task 2 · driangle
    Look up a task by ID or name and start working on it. Use when the user wants to pick up and execute a task.
    77 repo stars
  4. ▌
    Add Task 2 · driangle
    Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
    77 repo stars
  5. ▌
    Get Task 2 · driangle
    Get details of a specific task by ID or name. Use when the user wants to view or look up a task.
    77 repo stars
  6. ▌
    Next Task 2 · driangle
    Get the next recommended task to work on. Use when the user asks what to work on next or needs a task assignment.
    77 repo stars
  7. ▌
    List Tasks 2 · driangle
    List tasks from the project's taskmd files, with optional filters (status, priority, phase, group, owner). Use whenever the user asks what is pending, in progress, done, outstanding, assigned, high priority, or "on the plate" — including phrasings like "my tasks", "my todos" or "what's left", which refer to the project's task files and not to conversation memory.
    77 repo stars
  8. ▌
    Split Task 2 · driangle
    Split a large task into smaller sub-tasks. Accepts a task ID, evaluates complexity, and creates sibling task files if warranted.
    77 repo stars
  9. ▌
    Update Task 2 · driangle
    Update an existing task's fields (status, priority, title, tags, dependencies, etc.). Use when the user wants to modify a task's properties.
    77 repo stars
  10. ▌
    Verify Task 2 · driangle
    Run verification checks for a task and evaluate results. Use when the user wants to verify a task's acceptance criteria.
    77 repo stars
  11. ▌
    Import Todos 2 · driangle
    Discover TODO/FIXME comments in the codebase and convert selected ones into task files. Use when the user wants to turn code TODOs into tracked tasks.
    77 repo stars
  12. ▌
    Complete Task 2 · driangle
    Mark a task as completed. Use when the user wants to mark a task as done or complete.
    77 repo stars
  13. ▌
    Validate Tasks 2 · driangle
    Validate task files for format and convention errors. Use when the user wants to check their task files.
    77 repo stars
  14. ▌
    Get Task Status 2 · driangle
    Get only the metadata/status of a task without full details. Use when the user wants to quickly check a task's status, priority, or other metadata.
    77 repo stars
  15. ▌
    Divide And Conquer 2 · driangle
    Pick up a task and execute it using subagents to parallelize independent workstreams. Use when the user wants to work on a task with maximum concurrency.
    77 repo stars
  16. ▌
    Work · driangle
    Pick up the next task, execute it, verify it, mark it complete, and commit. Use when the user wants to work through tasks one at a time, or says 'do the next task', 'work on the next item', or invokes /work. Optionally accepts a task ID and/or custom instructions.
    77 repo stars
  17. ▌
    Commit · driangle
    Commit all uncommitted changes with an auto-generated conventional commit message. Use when the user asks to commit, save changes, or invokes /commit.
    77 repo stars
  18. ▌
    Pr Open · driangle
    Open a GitHub PR for the current branch. Generates a title and description from the diff, and respects the repo's PULL_REQUEST_TEMPLATE if one exists.
    77 repo stars
  19. ▌
    Migrate · driangle
    Perform codebase migrations: upgrade dependencies, swap libraries, adopt new APIs or patterns, and modernize legacy code. Use when the user wants to migrate, upgrade, swap a library, adopt a new pattern, or modernize code.
    77 repo stars
  20. ▌
    Pr Stack · driangle
    Split a large feature branch into multiple smaller PRs of max 20 files each. Use when the user wants to break up a big branch, split changes into stacked or parallel PRs, asks "how do I split this PR", mentions a branch has too many files, or wants a PR splitting strategy. Also triggers on phrases like "split this into PRs", "break up this branch", "chunk these changes", "PR plan", or "too many files in this PR".
    77 repo stars
  21. ▌
    Refactor · driangle
    Perform structured refactoring operations: extract module, split file, inline abstraction, rename symbol across codebase, simplify complex code, or reduce coupling. Use when the user wants to refactor code, extract a module, split a large file, or reorganize code structure.
    77 repo stars
  22. ▌
    Pr Review · driangle
    Review a GitHub PR and present findings as author-addressed comments. Use when the user asks to review a PR, gives a PR URL or number, or asks for code review feedback on a pull request. Triggers on phrases like "review this PR", "look at this pull request", "code review", or any GitHub PR link.
    77 repo stars
  23. ▌
    Pr Triage · driangle
    Generate a Slack-friendly triage report of open GitHub PRs for a team, author, or set of repos — pure-prompt variant of pr-review-report with no helper script. Use this skill whenever the user wants a PR review queue summary, a daily/standup PR digest, a reviewer triage list, or asks things like "what PRs does my team owe reviews on", "which of my PRs are waiting on review", "show me the team's open PRs", or "give me a PR status report for org X". The skill buckets each PR into exactly one of Needs attention / Ready to merge / In discussion / Awaiting review so reviewers can focus on what matters most.
    77 repo stars
  24. ▌
    Fix Feedback · driangle
    Address feedback about a bug or feature issue using a test-first workflow: reproduce with a failing test, then fix. Use when the user provides feedback, a bug report, or a user-reported issue and wants it verified and fixed.
    77 repo stars
  25. ▌
    Commit Msg · driangle
    Generate a one-line conventional commit message from staged changes. Use when the user asks for a commit message or invokes /commit-msg.
    77 repo stars
  26. ▌
    Audit · driangle
    Perform a comprehensive codebase audit covering security, privacy, data integrity, architecture, and code quality. Use when the user wants to audit the codebase, check for security issues, or review code quality.
    77 repo stars
  27. ▌
    Spec Decompose · driangle
    Decompose a spec, requirements document, or technical design doc into actionable task files. Use when the user provides a spec file and wants it broken down into tasks, work items, or a project plan. Also trigger when the user says things like 'break this down', 'create tasks from this spec', 'plan out this project', 'turn this into tasks', or 'decompose this into work items' — even if they don't say 'spec' explicitly.
    77 repo stars
  28. ▌
    Rebase Merge · driangle
    Rebase the current branch onto a target branch, resolve any conflicts, then fast-forward merge it into the target. Use when the user asks to merge a branch via rebase or invokes /rebase-merge.
    77 repo stars
  29. ▌
    Oddities · driangle
    Scan a scope of code for unconventional, strange, questionable, undocumented, or opaque things — latent bugs, unexpected complexity, inconsistencies, surprising design choices, and library/API workarounds. Produces a prioritized reading list, not a refactor plan. Use whenever the user wants to 'review' a directory/module/branch, flag 'weird' or 'suspicious' code, find 'red flags', spot 'code smells', or just understand what's odd in a slice of the codebase they're about to touch.
    77 repo stars
  30. ▌
    Setup Targets · driangle
    Bootstrap a project's checks to standard conventions: per-project build targets (compile, lint, format-check, test, build), enforced lint standards (max 200 lines per file, max 50 lines per function, layered import rules), top-level check/check-lite targets, a pre-commit hook for check-lite, and CI running check. Use when the user wants to add Makefile targets, set up CI-ready build commands, standardize project checks or lint rules, or bootstrap a new/existing repo to their check conventions.
    77 repo stars
  31. ▌
    Pr Description · driangle
    Generate a concise PR description based on the changed files and their content. Focus on summarizing the key changes and their impact, rather than providing a detailed line-by-line explanation.
    77 repo stars
  32. ▌
    Sync Worktrees · driangle
    Synchronize worktrees with main: rebase each worktree branch onto main, fast-forward merge it into main, then fast-forward every worktree branch back up to the final main. Use when the user asks to sync worktrees, merge worktrees into main, or invokes /sync-worktrees.
    77 repo stars
  33. ▌
    Dead Code · driangle
    Find dead code in the codebase: unused exports, orphaned files, unreachable code paths, unused dependencies, and stale feature flags. Use when the user wants to clean up unused code or identify candidates for removal.
    77 repo stars
  34. ▌
    API Review · driangle
    Review a library's public API for clarity, consistency, composability, predictability, edge-case handling, and correctness. Use when the user wants to review an API surface, check API design quality, or evaluate a library's exported interface. Designed for libraries and packages — not services, servers, or full applications.
    77 repo stars
  35. ▌
    Test Audit · driangle
    Review the project's test suite for legitimacy: detect tautologies, trivially-passing assertions, mocked-away logic, and other patterns that give false confidence in test coverage. Use when the user wants to verify their tests are meaningful.
    77 repo stars
  36. ▌
    Pr Review Report · driangle bundle
    Generate a Slack-friendly triage report of open GitHub PRs for a team, author, or set of repos. Use this skill whenever the user wants a PR review queue summary, a daily/standup PR digest, a reviewer triage list, or asks things like "what PRs does my team owe reviews on", "which of my PRs are waiting on review", "show me the team's open PRs", or "give me a PR status report for org X". The skill buckets each PR into exactly one of Needs attention / Ready to merge / In discussion / Awaiting review so reviewers can focus on what matters most.
    77 repo stars
  37. ▌
    Triage Dependabot · driangle
    Triage Dependabot security alerts: group by package, find high-payoff upgrades and removal candidates, then plan a fix for the one the user chooses.
    77 repo stars
  38. ▌
    Refactor Plan · driangle
    Produce a prioritized refactoring plan for the code you just worked with — each suggestion tagged with priority and effort, sorted most- to least-recommended. It recommends and ranks; it does not perform the changes. Use right after finishing a task in a codebase, when the user asks 'what should I refactor', 'what would you clean up here', 'give me a refactor plan', 'what are the follow-up improvements', or wants recommendations grounded in the files already touched during the session. Complements 'oddities' (a reading list) by producing an actionable, ranked plan.
    77 repo stars
  39. ▌
    Release · driangle bundle
    Create a new release by bumping versions, tagging, pushing, and generating release notes. Use when the user wants to release a new version.
    77 repo stars
  40. ▌
    New Eval · driangle
    Build a skival eval suite that benchmarks one taskmd skill — fixture, deterministic graders, four variants, smoke run, and a committed report. Use when adding a suite under evals/, benchmarking a skill, or measuring whether a skill actually helps.
    77 repo stars
  41. ▌
    Audit Docs · driangle
    Audit documentation coverage across CLI commands, web features, and configuration. Builds the CLI, discovers all commands/flags, checks web pages, and cross-references against docs/ and apps/docs/.
    77 repo stars
  42. ▌
    Do Task · driangle
    Look up a task by ID or name and start working on it. Use when the user wants to pick up and execute a task.
    77 repo stars
  43. ▌
    Add Task · driangle
    Create a new task file following the taskmd specification. Use when the user wants to add a new task to the project.
    77 repo stars
  44. ▌
    Get Task · driangle
    Get details of a specific task by ID or name. Use when the user wants to view or look up a task.
    77 repo stars
  45. ▌
    Next Task · driangle
    Get the next recommended task to work on. Use when the user asks what to work on next or needs a task assignment.
    77 repo stars
  46. ▌
    List Tasks · driangle
    List tasks from the project's taskmd files, with optional filters (status, priority, phase, group, owner). Use whenever the user asks what is pending, in progress, done, outstanding, assigned, high priority, or "on the plate" — including phrasings like "my tasks", "my todos" or "what's left", which refer to the project's task files and not to conversation memory.
    77 repo stars
  47. ▌
    Split Task · driangle
    Split a large task into smaller sub-tasks. Accepts a task ID, evaluates complexity, and creates sibling task files if warranted.
    77 repo stars
  48. ▌
    Update Task · driangle
    Update an existing task's fields (status, priority, title, tags, dependencies, etc.). Use when the user wants to modify a task's properties.
    77 repo stars
  49. ▌
    Verify Task · driangle
    Run verification checks for a task and evaluate results. Use when the user wants to verify a task's acceptance criteria.
    77 repo stars
  50. ▌
    Import Todos · driangle
    Discover TODO/FIXME comments in the codebase and convert selected ones into task files. Use when the user wants to turn code TODOs into tracked tasks.
    77 repo stars
  51. ▌
    Complete Task · driangle
    Mark a task as completed. Use when the user wants to mark a task as done or complete.
    77 repo stars
  52. ▌
    Validate Tasks · driangle
    Validate task files for format and convention errors. Use when the user wants to check their task files.
    77 repo stars
  53. ▌
    Get Task Status · driangle
    Get only the metadata/status of a task without full details. Use when the user wants to quickly check a task's status, priority, or other metadata.
    77 repo stars
  54. ▌
    Divide And Conquer · driangle
    Pick up a task and execute it using subagents to parallelize independent workstreams. Use when the user wants to work on a task with maximum concurrency.
    77 repo stars