Results for “pr-description”

Turns a process description into a complete Standard Operating Procedure document with numbered steps, decision points, checklists, and troubleshooting guidance.

Provides a structured template for creating new Agent Skills, including sections for description, activation criteria, core concepts, practical guidance, and integration notes.

Create, update, and comment on GitHub pull requests with a focus on material impact, safety, and human reviewability.

Guides creating small, issue-linked pull requests with conventional branch naming, commit messages, and structured descriptions, plus a review cycle.

Author pull requests with intent-separated commits, blast-radius disclosure, and verification evidence. Load when opening a PR, writing a PR description, separating refactor from feature commits, or summarizing a change set for review. Also triggers on "write the PR", "PR body", "intent-separated commits", "split refactor from feature", "pr summary", or after safe-change cycles complete. Extends git-workflow-and-versioning — does not replace it.

Proposal pricing workflow producing defensible line-item, tiered, or value-based pricing with calibration and sanity checks. Use when the user needs a quote, estimate, tier packages, pricing strategy, rate calibration, or discount modeling for a proposal brief. Triggers: 'price this proposal', 'build tiered pricing', 'line-item estimate', 'value-based price', 'calibrate rates', 'sanity check this quote'.

Generates a concise bullet-point summary of branch changes for a pull request description, grouping related commits by theme and verifying details against actual files.

Creates animated flow diagrams from articles, workflow notes, architecture sketches, or process descriptions using a JSON specification and a local Python/Pillow renderer.

Turns messy business process descriptions into structured workflows, classifies each step for automation potential using a GREEN/YELLOW/RED framework, and produces a prioritized automation roadmap with time savings estimates.

Drafts clear, professional emails ready to copy and paste — from a brief description of the situation, audience, and intent. Use when asked to write, draft, or compose an email, reply to a message, or suggest how to phrase something professionally.

Breaks natural-language problem descriptions into sub-tasks suitable for DAG nodes. The entry point of the meta-DAG. Identifies phases, dependencies, parallelization opportunities, and vague/pluripotent nodes that can't yet be specified. Uses domain meta-skills when available. Activate on "decompose task", "break down problem", "plan workflow", "what are the steps", "sub-tasks", "task breakdown". NOT for executing the decomposed tasks (use dag-runtime), building the DAG structure (use dag-planner), or matching skills to nodes (use dag-skills-matcher).

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.