Results for “branch-summary”

Creates a pull request from the current feature branch with a structured summary, test results, and change description.

Produces neutral, section-pinned U.S. legislative bill summaries translating statutory language into plain terms with identifying data, provisions, fiscal impacts, and controversy. Use when summarizing bills, analyzing proposed legislation, preparing bill briefs, digesting committee reports or fiscal notes, or writing legislative updates.

Create a git branch following Sentry naming conventions, automatically deriving the branch type and description from current work context.

Use to write Cell's Summary — a single unstructured paragraph of ≤ ~150 words that conveys the complete story, the mechanism, and the broad significance, quantified and readable by a general life-scientist. Late-stage polish.

Brief

Composite skill — one-pass cleanup of stale local branches, dead worktrees, merged branches, and abandoned remote PR branches. Chains `git fetch --prune` → `clean_gone` (kill [gone] branches) → worktree prune + offer-to-remove dead worktrees → list-and-delete branches merged to main and release → delete remote PR branches whose PRs merged >7 days ago. Use instead of running `clean_gone` alone — that only catches half the rot. Daily-friction composite; fires on "clean up branches", "branch hygiene", "stale worktrees", and on session start when local branch count > 30.

Generates structured summaries of Non-Disclosure Agreements, extracting parties, confidential information scope, permitted disclosures, term/survival, breach remedies, and risk flags. Use when summarizing NDAs, reviewing confidentiality agreements, distilling NDA obligations, or onboarding stakeholders to NDA terms.

Summarizes U.S. commercial lease agreements into structured transactional abstracts. Use when asked for a commercial lease summary, lease abstract, key lease terms, rent schedule review, default/termination analysis, or lease handoff. Produces party-to-obligation mappings, financial mechanics, risk flags, and critical date calendars.

Create, refresh, and rewrite PR titles and descriptions following Sentry conventions, focusing on reviewer-facing content that describes the full branch diff.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist and attack surface mapping.

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

Review local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist-driven process.

Structures git workflow practices for committing, branching, resolving conflicts, and organizing work across multiple parallel streams.

Assemble a Jira/Linear/GitHub-Issue body from recent commits, diff, and branch context

Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary, with per-group history, user profiles, and privacy guardrails.

Brief

阅读理解小说文本，总结成流畅的故事大纲。适用于小说初筛选、生成500-800字故事大纲

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, using a structured checklist and verification process.

总结 PR 变更内容，概述主要改动点并生成变更说明。

Guides Git version control practices: branching strategies, commit conventions, merge vs rebase, conflict resolution, and pull request workflows for collaborative teams.

基于故事文本提炼主要情节与要点，生成完整故事梗概。适用于快速了解故事内容、剧本改编、项目推介

Consolidate all update audits (claims, product-mentions, topic-gaps) into a single revised article. Preserves the original voice; applies only the audited changes.

Produce a plain-language manual test plan from the context supplied to it — an executive summary, a high-level list of named tests, and a detail section per test with the steps a person follows by hand and the outcomes they should expect. Use when you want to create, draft, generate, or outline a manual test plan, manual QA steps, hands-on verification steps, or an acceptance walkthrough for a feature, change, branch, plan, or PR. When the plan holds more than five tests and at least two natural categories emerge, both the test list and the detail sections are organized under plain-language categories. When nothing in the supplied context can be manually tested, it says so and asks for more context instead of producing a document. Does not analyze code for automated test coverage gaps — use automated-test-planning. Does not write test code — use tdd. Does not review code quality — use code-review. Does not stress-test an existing plan — use iterative-plan-review.