inanna-malick

Canonical version: proptest-praxis in agent-skills. Use that for the most up-to-date version. The original prompt is preserved below.

Agents and property tests: investigation prompt

Use these instructions in the target repository. Incorporate any maintainer concerns, suggested targets, and repository-specific guidance I provide. Own the investigation and keep exploring as findings suggest new targets.

1. Objective and deliverables

Find correctness bugs across the repository by building and running property-testing machinery. Target Rust proptest; use the repository's equivalent framework for other languages. Prioritize executable checks that can explore many inputs and operation histories without spending LLM tokens analyzing each case.

haileyok

---
name: code-review
description: Review a pull request (or the current branch) with TWO parallel reviewer subagents on gpt-5.5(high) — a standard reviewer and an adversarial reviewer. Merge their findings only after both return; deliver an in-chat summary always and post to the PR only with consent. When reviewing your own branch, iterate on the feedback and re-invoke until no findings remain.
disable-model-invocation: false
tags:
  - productivity
polytoken: true
---

# Code Review

samhenrigold

# Owning binary : TextComposerRuntime
# Status        : NEW in iOS 27 (not in 26.5.1)
# Source        : embedded __cstring in dyld_shared_cache_arm64e (24A5355q)
======================================================================

    # Task Overview:
    You are a composition agent that helps users create personalized written content (emails, messages, documents, posts, stories, etc.)

    As an Assistant, you must:
    1. Analyze the request to determine if you have sufficient information

jandem

#include <pthread.h>
#include <sys/mman.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <stdatomic.h>
#include <errno.h>
#include <stdint.h>
#include <sched.h>

davidbarsky

name	rustdoc
description	Rust documentation conventions (RFC 1574). Apply when writing doc comments on public Rust items. Covers summary sentences, section headings, type references, and examples.

Rust Documentation Conventions (RFC 1574)

Apply these rules when writing doc comments (///) on public Rust items.

Summary Sentence

arianvp

Asynchronous post-build-hook

this hook queues up store paths on a unix domain socket and then spawns a service to actually push the store path to the cache through socket activation

works on MacOS and Linux

riwsky

#!/bin/bash

# Exit immediately if a command exits with a non-zero status
set -e

jj fix

# Get the list of mutable branches that are reachable from the current branch
# (i.e. that are between us and main).
branches=$(jj branch list -r 'reachable(@,mutable())' --template 'name ++ "\n"')

Innf107

{-# LANGUAGE RankNTypes, PatternSynonyms, GADTs, ViewPatterns, LambdaCase, ScopedTypeVariables #-}
module Main where
    
import Data.Map as Map
import Control.Monad (ap, liftM)
import Data.IORef

data ComeFromOp a where
    Line :: Int -> ComeFromOp ()
    LiftIO :: IO () -> ComeFromOp ()

denisdefreyne

Person = new Class {{

  firstName: :attr,

  lastName: :attr,

  fullName: function {
    `${this.firstName} ${this.lastName}`
  },

c0deaddict

{ lib, config, pkgs, ... }:

with lib;

let

  veth = "veth-vpn";
  hostIp = "10.0.0.1/24";
  guestIp = "10.0.0.2/24";