Namanyay Goel namanyayg

name	security-incident-remediation
description	Investigate a security alert or incident roundup, identify affected software in the user's environment, apply and verify authorized fixes, and document remaining incident-response and manual actions. Use for requests to audit, patch, upgrade, or respond to reported vulnerabilities and supply-chain compromises.

Security incident remediation

By Namanyay Goel.

Turn a security alert into verified fixes and an actionable handoff. Do the authorized work yourself; do not stop at a list of recommendations when you can inspect, patch, and test the affected projects.

You are an expert in all programming languages, frameworks, libraries, web technologies, databases, and operating systems.
Always begin your responses with "Sir".
Never modify code that is irrelevant to the user's request. Think carefully before making any changes.
When making changes, consider:
1. Relevance to Request: Are you editing code unrelated to the user's request? If so, do not modify it.
2. Scope Adherence: Only make changes directly relevant to the user's request. For example, if asked to add a new feature, focus solely on that feature without altering other aspects like the login experience or unrelated UI elements.
3. Avoid Unnecessary Changes: If you feel compelled to make unnecessary changes, stop and inform the user why.
Never replace code blocks or snippets with placeholders like # ... rest of the processing .... When modifying a file, always provide the full content with your changes.
**You're allowed to disagree with the user and seek clar

Date: [date]

Between me, Namanyay Goel
and you, [customer name]

Summary:

I’ll always do my best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. I’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.

So in short;

	'use server'

	import { revalidatePath } from 'next/cache'
	import { redirect } from 'next/navigation'
	import prisma from '@/lib/prisma'

	import { auth } from '@/auth'
	import { ServerActionResult, type ChatMetadata, type Chat } from '@/lib/types'
	import { type ChatHistory } from '@/lib/store'
	import { TokenUsage } from 'ai'

	<?php

	$branchname = $_GET['branch'];

	if (!$branchname) {
	echo "Please enter a branchname, ?branch=<name>";
	return false;
	}

	$command = 'cd <directory> && git checkout ' . $branchname;

	### Keybase proof

	I hereby claim:

	* I am namanyayg on github.
	* I am nmn (https://keybase.io/nmn) on keybase.
	* I have a public key whose fingerprint is 10AD D5BC 5D61 3EEC 7225 917D 0FE5 E279 736A 5493

	To claim this, I am signing this object:

	<?php

	$payload = '';
	if ( isset($_POST['payload']) ){
	$payload = json_decode($_POST['payload']);
	} else {
	return false;
	}

	$repo = $payload->repository;

	<?php
	require('phpQuery-onefile.php');

	$page = phpQuery::newDocumentFileHTML('http://coinmarketcap.com/');

	$cryptoprices = 'var cryptoprices = {';

	$cryptoprices .= 'markets:[';

	foreach( pq('tbody tr') as $row ) {