vesan

name	create-pr
description	This skill should be used when the user asks to "create a PR", "open a pull request", "make a PR", "submit a PR", "push a PR", or any variation of creating/opening a pull request. The skill focuses on extracting the INTENT behind changes and creating meaningful PR descriptions.
allowed-tools	Bash Read Write Grep Glob AskUserQuestion

Pull Request Creation

vesan

require "amazing_print"
class Debug
  attr_reader :messages, :before_gc_stats, :after_gc_stats, :time_report, :mem_report

  def initialize(with_sql: false, with_stack: false, store_file: false, console_print: false, output_path: nil, context: nil, file_prefix: nil, messages: [])
    @with_sql = with_sql
    @with_stack = with_stack
    @console_print = console_print
    @context = context
    @messages = messages

vesan

// Types for the result object with discriminated union
type Success<T> = {
  data: T;
  error: null;
};

type Failure<E> = {
  data: null;
  error: E;
};

vesan

function current_dir() {
    local current_dir=$PWD
    if [[ $current_dir == $HOME ]]; then
        current_dir="~"
    else
        current_dir=${current_dir##*/}
    fi
    
    echo $current_dir
}

vesan

#
# Copyright (c) nexB Inc. and others. All rights reserved.
# SPDX-License-Identifier: Apache-2.0
# See http://www.apache.org/licenses/LICENSE-2.0 for the license text.
# See https://aboutcode.org for more information about nexB OSS projects.
#


import getpass
from traceback import format_exc as traceback_format_exc

vesan

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

vesan

class OfficeAPIError < StandardError; end;

class OfficeAPITimoutError < StandardError
  def initialize(msg = "Office API timed out")
    super(msg)
  end
end

class OfficeAPI
  attr_accessor :access_token, :messages_filter, :mail_box, :fetch_from

vesan

class ApplicationController < ActionController:Base
  extend ControllerMacros
end

vesan

# Rails production setup via SQLite3 made durable by https://litestream.io/ 
# Copy this to Dockerfile on a fresh rails app. Deploy to fly.io or any other container engine. 
#
#  try locally: docker build . -t rails && docker run -p3000:3000 -it rails
#
#  in production you might want to map /data to somewhere on the host, 
#  but you don't have to!
# 
FROM ruby:3.0.2

vesan

import React from 'react';

import {
  actions,
  makePropGetter,
  ensurePluginOrder,
  functionalUpdate,
  useConsumeHookGetter,
  useGetLatest
} from '../../react-table/utils';