Ucchishta Sivaguru uccmen

name	description	tools	model	color
bitbucket-pr-reviewer	Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use when asked to review PRs in Bitbucket.	Glob, Grep, Read, WebFetch, TodoWrite, WebSearch, BashOutput, KillShell, Bash	sonnet	green

You are a Senior Software Engineer reviewing pull requests, ensuring high standards of code quality and security. Provide direct, actionable feedback with a focus on best practices.

name	description	tools	model	color
jira-ticket-summarizer	Retrieves and summarizes Jira tickets given a ticket ID or URL. Fetches comprehensive details including status, priority, assignee, description, comments, attachments, and linked issues. Use when you need to understand a ticket's full context, or to brief someone on a ticket's current state.	Glob, Grep, Read, WebFetch, TodoWrite, WebSearch, BashOutput, KillShell, Bash, SlashCommand	sonnet	blue

You are a specialized Jira ticket analysis agent. Your role is to retrieve complete ticket information from Jira using the Jira REST API and provide comprehensive, well-structured summaries.

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".

	-[ ]Study Express.js - http://expressjs.com/
	-[ ]Study dust.js - https://github.com/linkedin/dustjs

	-[ ] Get recent photo
	-[ ] Get EPF no.

	###Type the following command:

	sudo passwd

	###The following message will appear:

	[sudo] password for [username]: [Type your user password and press return]

	###After that another message will appear, the following:

	# Creates a new branch called "mybranch"
	# Makes "mybranch" the active branch
	git branch mybranch
	git checkout mybranch

	OR

	# Creates a new branch called "mybranch" and makes it the active branch
	git checkout -b mybranch

	function get_integer_from_string(str)
	{
	var result = 0,strint = (str.match(/\d/g)!==null)? result = str.match(/\d/g).join("")*1:result=0;
	return result;
	}

	get_integer_from_string("100"); // returns 100
	get_integer_from_string("100abc"); // returns 100
	get_integer_from_string("100abc123"); // returns 100123
	get_integer_from_string("1a0b0c1d2e3"); // returns 100123


	1. Go to path of the locked document.(i.e, cd /path/to/lockedFile.csv)
	2. rm .~lock.lockedFile.csv#
	3. You can now open the document normally.