jwiegley

60 mods across 2 repositories, 108 stars between them.

meeting-notes

50

jwiegley/claude-prompts

Command

You are a precise meeting notes analyst designed to transform raw meeting notes into structured, actionable intelligence. Your core mandate is rigorous adherence to factual accuracy—analyze only what is explicitly present in the notes provided.

20 5mo ago A 3 tokens

nix-rebuild

51

jwiegley/claude-prompts

Command

I cannot rebuild the current Nix system using ./build system. Use nix-pro to diagnose and resolve the issue.

20 5mo ago A 0 tokens

prepare-with

53

jwiegley/claude-prompts

Command

Use $ARGUMENTS to deeply analyze and understand the current project, so that you may provide expert guidance on the construction of a CLAUDE.md file that may be used to prepare future sessions for modification and improvement of the code here. Use sequential-thinking and Perplexity MCP as much as needed to research…

20 5mo ago A 0 tokens

productize

55

jwiegley/claude-prompts

Command

Command "productize" from jwiegley/claude-prompts, covering haskell, rust, c++, python and bash.

20 5mo ago A 0 tokens

proofread

56

jwiegley/claude-prompts

Command

Task: Review and correct English language errors in all Markdown, Org-mode and other text files within this project.

20 5mo ago A 0 tokens

push

57

jwiegley/claude-prompts

Command

I want you to /commit (using the prompt defined by the commit command) all of your work in a series of logically delineated commits, and then create a PR for this work and push it to GitHub.

20 5mo ago A 0 tokens

query-builder

58

jwiegley/claude-prompts

Command

Use the sql-pro and the mssql MCP to help answer this question. Never reveal table data in this chat, only reference the schema in order to build me an SQL query that I can run myself to obtain the actual data. Treat all of the data in the database as if it were highly secret and security sensitive, and never reveal…

20 5mo ago A 0 tokens

rebase

60

jwiegley/claude-prompts

Command

/heavy I want to Git rebase the current working tree onto the $ARGUMENTS branch. Use haskell-pro to analyze and resolve these conflicts in a way that preserves the semantics of the incoming changes, while maintaining the intent of the current working tree's work. Continue until the branch is fully rebased.

20 5mo ago A 0 tokens