THE PORTFOLIO OF NAZARETH KESHISHIANENGINEERING / WITH INTENT

Less friction.
More forward.

I build tools and systems that help engineering teams ship.

Explore my work A little about me ↓

Senior Release Engineer 2Developer tools · Platform · AI automation

FIG. 01 / FROM IDEA TO SHIPPED

● ● ●change.tsTS

const next = build({
context: 'understood',
checks: 'verified',
intent: 'ship'
});

// make the next step easier

VERIFICATION

✓Ready for what’s next.

UNDERSTAND → BUILD → VERIFY

SHIP IT.

A LITTLE STRUCTURE.
A LOT MORE MOMENTUM.

SOFTWARE THAT HELPS PEOPLE BUILD SOFTWARE.SCROLL TO EXPLORE

01 / PUBLIC PROJECTS

Built to be
opened.

Libraries, experiments, and reusable tools.
A selection of projects you can explore on GitHub.

01 / A BETTER INTERFACE

● ● ●index.ts

import JiraApi from 'jira-ts';

const jira = new JiraApi(config);
const issue = await jira.findIssue(
  'PROJ-123'
);

TypeScriptESM / v2 + v3

{ } TYPES INCLUDED

LIBRARY / TYPESCRIPT

jira-ts

A modern TypeScript client for Jira Cloud REST APIs v2 and v3. A clean-room rewrite of the legacy Jira client with ESM and bundled types.

Inside the project +

Legacy integration code needs a modern path forward. This client preserves familiar method names while adding v3 APIs and plain-text-to-ADF comment handling. Its HTTP dependency is limited to undici, keeping the runtime surface small. The repository includes tests and CI.

02 / CONTEXT BEFORE OUTPUT

✳

SKILL.md

A sharper
second look.

01 Understand the context

02 Look for failure patterns

03 Report what matters

CONTEXT
FIRST ↗

AI / REVIEW WORKFLOWS

ai-skills

Reusable instructions for AI-assisted code analysis. The Android ANR detector focuses reviews on code that could block the UI thread.

Inside the project +

Broad review prompts can miss specific failure patterns. This skill packages context, analysis steps, and a reporting format around main-thread I/O, synchronization, expensive computation, and lifecycle pitfalls. Structured guidance makes the review scope explicit; findings still need engineering verification.

03 / EXPLORING THE POSSIBLELATTICE-BASED SIGNATURES
FALCON / BITCOIN SIMULATION

RESEARCH / PYTHON

Falcon-Bitcoin

An exploration of Falcon post-quantum signatures in a Bitcoin simulation, with Python experiments and system diagrams.

Inside the project +

This research asks how a different signature scheme might fit Bitcoin-style transactions. The repository contains simulation wrappers and separate Falcon and legacy simulation scripts. Keeping the experiment in a simulation makes the integration easier to explore; it is not a claim of production Bitcoin compatibility or security certification.

More public repositories 14 REPOSITORIES

02 / A LITTLE ABOUT ME

There’s a person
behind the pipeline.

I’m a Senior Release Engineer 2 at Picsart.

My interests span release engineering, developer tooling, backend systems, and AI-assisted automation. I enjoy finding ways to make everyday engineering simpler and more dependable.

Outside my day-to-day role, my public projects give me room to explore API design, structured AI reviews, and cryptography. For me, a useful tool keeps helping long after the first feature ships.

Find me on LinkedIn ↗Download CV PDF ↓

03 / CAPABILITIES

A toolkit with a purpose.

01 / CONNECT

Make systems talk.

Backend services, APIs, webhooks, and bots that carry context across engineering tools.

TypeScript · JavaScript · Node.js · Express · REST · GraphQL · MongoDB

02 / DELIVER

Make delivery repeatable.

Shared pipelines, build tooling, repository checks, and mobile release workflows.

GitLab CI/CD · Jenkins · Shell · pnpm · Turborepo · Docker · Kubernetes configuration

03 / UNDERSTAND

Make context useful.

Dashboards and AI integrations that help engineers find information and decide what to do next.

React · Vite · Tailwind · React Query · Recharts · MCP · OpenAI · Anthropic

04 / HOW I WORK

Understand. Build.
Verify. Maintain.

01Start with the actual problem. Understand the workflow before adding another service or abstraction.

02Design for the unhappy path. External APIs fail. Clear boundaries and reliable failure behavior matter.

03Make verification mean something. Use tests, mocking, coverage analysis, and mutation-based verification to challenge assumptions—including AI-generated code.

04Follow the change through. Implementation, review, deployment configuration, and ongoing maintenance are part of the same job.

05 / LET’S CONNECT

Let’s make
the next connection.

Have an engineering workflow worth improving?
I’d be glad to hear about it.

Say hello on LinkedIn ↗Explore GitHub ↗

Less friction.More forward.

Built to beopened.

jira-ts

A sharpersecond look.

ai-skills

Falcon-Bitcoin

There’s a personbehind the pipeline.

A toolkit with a purpose.

Make systems talk.

Make delivery repeatable.

Make context useful.

Understand. Build.Verify. Maintain.

Let’s makethe next connection.

Less friction.
More forward.

Built to be
opened.

A sharper
second look.

There’s a person
behind the pipeline.

Understand. Build.
Verify. Maintain.

Let’s make
the next connection.