Results for “gatherup”
18 skillsstandup
Facilitates a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.
· bundle
pk-standup
Generate today's standup: what was done, what is in progress, what comes
0
teaming-finder
Find adjacent vendors and subs (not top market primes) who fill a capability gap against a displacement target using USASpending flows and SAM entity signals. Use when user defines a teaming gap and wants vault-ready partner shortlist with citations.
0
handoff
Generate a project-level context snapshot for resuming work in a fresh session
1 · bundle
catchup
Quickly refreshes project state when resuming work by reporting git status, recent commits, environment, memory staleness, pending tasks, and red flags.
0
grill-me
A relentless interview to sharpen a plan or design.
6
cleanup
Tears down a merged PR's worktree and feature branch, verifying merge status on GitHub before deleting local and remote branches and switching back to the main worktree.
1
standup-context
Writes a structured standup update as a session.standup LogEntry — capturing what was done, what is in progress, what comes next, and any blockers. Use when the user says "write a standup", "standup update", "what did I do today", "write a status update for the team", or at the end of a session on projects that run daily standups.
0 · bundle
law-of-common-region
Group interface elements using containers, backgrounds, and boundaries based on the Gestalt Law of Common Region.
1.7k
handoff-diet
Meta-skill codifying the no-wakeup-polling pattern. Describes the ScheduleWakeup anti-pattern, the fix (--auto merge + detached watcher), and when to still use wakeups. Reduces handoff spam by 80%.
1 · bundle
tidy
Triggered by "tidy up", "clean up transactions", "categorize uncategorized", "organize my transactions"
2
arrange
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
7
pickup
Start-of-session context pickup. Reads the latest handoff file and resumes work where the last session left off. Run this at the start of a new session if a handoff file exists.
8
catchup
Rebuilds working context after a session clear by reading git history, plans, and beads issue state, then produces a visible briefing.
7 · bundle
status-briefing
Generates a concise status briefing after session-start reconciliation — synthesizing current state, open decisions, key risks, and today's priority actions. Use at session start, for "pk-resume", a briefing, catch-up, or today's focus.
0 · bundle
session-handover
Write an end-of-session handover LogEntry capturing current state, open threads, next action, and git context for session continuity.
0 · bundle
branch-hygiene
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.
1 · bundle
37signals-way
Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
28 · bundle