Skip to content

Instantly share code, notes, and snippets.

View nzakas's full-sized avatar

Nicholas C. Zakas nzakas

View GitHub Profile
@nzakas
nzakas / summarize-issue.prompt.md
Created July 24, 2025 16:11
Summarize GitHub Issue Prompt
mode tools
agent
github

Your task is to generate a summary of all comments from a specific GitHub issue. The summary should be concise, capturing the essence of the discussion while remaining neutral and objective.

Steps:

  • Use get_issue_comments to read all comments from the specified GitHub issue.
@nzakas
nzakas / thinking-cap.chatmode.md
Created July 22, 2025 19:11
Thinking Cap Mode for GPT-4.1
description model tools
Thinking Cap Mode
GPT-4.1
changes
codebase
editFiles
extensions
fetch
findTestFiles
githubRepo
new
problems
runCommands
runNotebooks
runTasks
runTests
search
searchResults
terminalLastCommand
terminalSelection
testFailure
usages
vscodeAPI

I will present you with a task to complete. Think deeply about the requirements and constraints, and generate a plan to accomplish the task. The plan must include searching the codebase for relevant code regardless of the file type, and then writing the code, tests, and documentation to complete the task. Implement the plan without asking for further input.

@nzakas
nzakas / eslint.config.mjs
Created May 27, 2025 16:08
Using eslint-config-airbnb with ESLint v9
/*
* To install `eslint-config-airbnb`, run:
* npm install -D eslint-config-airbnb --force
*
* The --force flag is necessary because `eslint-config-airbnb` has a
* peer dependency on `eslint@^8.0.0`, which may conflict with other
* packages in your project.
*
* After installing, you'll need to use `npm install --force` when
* installing other packages to avoid conflicts with the peer dependencies.
@nzakas
nzakas / pancakes.md
Created April 10, 2020 21:47
Pumpkin pancakes

Pumpkin Pancakes Recipe

Ingredients

  • 1/4 cup pumpkin puree
  • 1/4 cup almond milk
  • 1/4 cup water
  • 3 eggs
  • 1 tbsp coconut oil (melted)
  • 1 tsp vanilla
@nzakas
nzakas / salary.csv
Last active April 21, 2023 10:39
Salary History Table
Year YOE Company State Title Starting $ Ending $ Signing $ Options
2000 0 Radnet, Inc. MA Webmaster $48,000 $55,000 - ?
2001 0 Radnet, Inc. MA UI Developer $62,500 $62,500 - -
2001 0 MatrixOne, Inc. MA UI Designer/Developer $68,000? ? $2,000 ?
2003 3 MatrixOne, Inc. MA Senior Software Engineer ? $75,000? - -
2005 5 Vistaprint, Inc. MA Lead Software Engineer $82,000? $98,000 - 3,000
2006 6 Yahoo, Inc. CA Senior Front-end Engineer $115,000 ? $10,000 3,500
2008 8 Yahoo, Inc. CA Principal Front-end Engineer ? ? - -
2011 11 Yahoo, Inc. CA Presentation Architect ? $165,000? - -
2013 13 Box, Inc. CA Staff Software Engineer $175,000 ? $25,000 50,000
### Keybase proof
I hereby claim:
* I am nzakas on github.
* I am nzakas (https://keybase.io/nzakas) on keybase.
* I have a public key ASDOjUn5w1cYZhamvMdllaGhLM-jbBo23c1TAW6oUYLslwo
To claim this, I am signing this object:
@nzakas
nzakas / environment.log
Created April 1, 2018 02:33
Netlify Function error log
Nicholas@Patriot MINGW64 ~
$ node -v
v8.10.0
Nicholas@Patriot MINGW64 ~
$ npm -v
5.6.0
@nzakas
nzakas / techleadbook.md
Created March 20, 2018 20:44
Tech Lead Book

Tech Lead Book

  1. Introduction
  2. What is a Tech Lead?
  3. The Tech Lead Mindset
  4. Becoming a Tech Lead
  5. Working Cross-Functionally
  6. The Art of Delegation
  7. Technical Best Practices
  8. Effective Decision Making
@nzakas
nzakas / gist:edbb30b7f3a15ace61e3eb68013603ee
Created September 20, 2016 20:53
GitHub blocking push to master branch
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: At least one approved review is required.
To [email protected]:eslint/typescript-eslint-parser.git
! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to '[email protected]:eslint/typescript-eslint-parser.git'
@nzakas
nzakas / githubpainpoints.md
Created June 30, 2016 18:47
An overview of my pain points with GitHub

GitHub Pain Points

This is my feedback on using GitHub to manage a popular project (ESLint). Topics are presented in no particular order. In general, everything I say about issues also refers to pull requests.

For each problem I've suggested a solution. I realize that actually building out a solution is a complex process and my suggestions do not reach the level of detail sufficient for implementation purposes. It's just to give you an idea of the direction I'm thinking.

Problem: No good way to distinguish new issues from "accepted" issues

Users are opening new issues every day, and these issues automatically bubble to the top of the issues list by default. We do label issues that we're committed to doing as "accepted", but if there are enough new issues, you don't even see those until the second page of issues. Why is this a problem? In a word: distraction.