Skip to content

Instantly share code, notes, and snippets.

View rjmurillo's full-sized avatar
💭
I may be slow to respond.

Richard Murillo rjmurillo

💭
I may be slow to respond.
View GitHub Profile
You are a team of three expert software development personas assigned to a stakeholder to collaboratively gather requirements and produce a software specification document that is clear, visual, and actionable.
## 🧍Stakeholder Overview
* **Profile:** Non-technical and easily overwhelmed.
* **Needs:** Clarity, simplicity, and limited information at a time.
* **Constraint:** Each expert must ask *only one question per turn* and avoid technical jargon.
---

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

  • Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
  • Select "Create new custom chat mode file"
@burkeholland
burkeholland / 4.1.chatmode.md
Last active August 13, 2025 11:46
4.1 Beast Mode v2
description tools
4.1 Beast Mode
changes
codebase
editFiles
extensions
fetch
findTestFiles
githubRepo
new
openSimpleBrowser
problems
readCellOutput
runCommands
runNotebooks
runTasks
runTests
search
searchResults
terminalLastCommand
terminalSelection
testFailure
updateUserPreferences
usages
vscodeAPI

You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.

@stilist
stilist / monitoring.md
Last active October 27, 2020 05:36
Notes on site reliability

Monitoring

Alerting

  • base rate fallacy: given 1% false positive, 1% false negative, and 99.9% uptime: 9.1% chance positive predictive value (true positive)
  • sensitivity (% true positives) vs specificity (% not false positive)
  • ‘Alert liberally; page judiciously. Page on symptoms, rather than causes.’
  • ‘An alert should communicate something specific about your systems in plain language: “Two Cassandra nodes are down” or “90% of all web requests are taking more than 0.5s to process and respond.”’
  • ‘Not all alerts carry the same degree of urgency.’
  • ‘Many alerts will not be associated with a service problem, so a human may never even need to be aware of them. […] should generate a low-urgency alert that is recorded in your monitoring system for future reference or investigation but does not interrupt anyone’s work.’
@kpettijohn
kpettijohn / ghprb_auth.groovy
Last active June 23, 2019 04:38
Configure GitHub Pull Request Builder Jenkins plugin with Groovy
// ghprb 1.29.2
import java.lang.reflect.Field
import jenkins.model.*
import org.jenkinsci.plugins.ghprb.*
def descriptor = Jenkins.instance.getDescriptorByType(org.jenkinsci.plugins.ghprb.GhprbTrigger.DescriptorImpl.class)
Field auth = descriptor.class.getDeclaredField("githubAuth")
auth.setAccessible(true)
@jamtur01
jamtur01 / ladder.md
Last active July 28, 2025 07:12
Kickstarter Engineering Ladder
@ghinda
ghinda / git-delete-local-branches.sh
Created March 19, 2015 21:08
Delete all local tracking git branches for which the origin remote branches have been deleted
git for-each-ref --format='%(refname:short)' refs/heads/* | while read branch; do BRANCH_EXISTS=$( git ls-remote --heads origin $branch | wc -l ); if [ $BRANCH_EXISTS -eq 0 ]; then git branch -D $branch; fi;done