A company-wide collection of AI-powered tools and utilities built by engineers, for engineers — supercharging how we write, review, plan, and ship code.
We spend a lot of time on repetitive, low-value tasks — copying Jira tickets into documents, context-switching between tools, writing boilerplate. AI can automate most of that.
This repository is our shared space to build, maintain, and improve those automation tools. Everyone on the engineering team is invited to contribute — whether that's a small bug fix, a new feature idea, or an entirely new tool.
Small contributions compound. Your workflow hack could save every engineer hours per week.
| Tool | Description | Status |
|---|---|---|
| jira-to-md-extension | Chrome extension that converts Jira tickets into structured Markdown files with one click | ✅ Stable |
| Your tool here | Got a workflow automation idea? Open an issue or submit a PR | 💡 Wanted |
Converts any Jira ticket (classic or modern Atlassian) into a clean Markdown file, ready to paste into docs, PRs, or AI prompts.
Install (Developer Mode)
- Clone this repository:
git clone https://github.com/your-org/ai-tooling.git
- Open Chrome and navigate to
chrome://extensions - Enable Developer mode (top-right toggle)
- Click Load unpacked and select the
jira-to-md-extension/folder - Navigate to any Jira ticket and click the extension icon
What it does
- Extracts ticket title, description, acceptance criteria, assignee, priority, labels, and more
- Converts Jira-flavoured HTML (both classic and modern UI) to clean Markdown
- Lets you copy to clipboard or download as a
.mdfile - Works on
*.atlassian.netand self-hosted Jira instances
We want this to be a living project. Contributing is easy — even if you've never contributed to an open source project before.
- Found a bug? Open an issue with steps to reproduce
- Have an idea? Describe the tool or feature you wish existed
- Built something useful? Submit a PR — even rough drafts are welcome
- Improved an existing tool? Great, open a PR with a clear description
- Fork the repository (or clone directly if you have write access)
- Create a branch for your change:
git checkout -b feat/my-new-tool
- Make your changes — keep each PR focused on one thing
- Test your changes manually before submitting
- Open a Pull Request with a clear title and description of what the change does and why
Each tool lives in its own top-level folder:
ai-tooling/
├── jira-to-md-extension/ ← existing Chrome extension
├── your-new-tool/ ← add yours here
│ ├── README.md ← explain what it does and how to use it
│ └── ...
There are no strict technology requirements. Use whatever fits the problem — shell scripts, browser extensions, Python scripts, VS Code extensions, etc.
Please include a README.md in your tool's folder with:
- What problem it solves
- How to install / run it
- Any known limitations
- Prefer clarity over cleverness — other people will maintain this
- Comment non-obvious logic
- Keep dependencies minimal
Not sure what to build? Here are areas where automation would have high impact:
- PR description generator — auto-draft PR descriptions from commit history or diff
- Code review assistant — summarise large diffs before reviewing
- Meeting notes formatter — clean up raw notes into structured action items
- Ticket estimator — suggest story points from ticket description
- Changelog generator — build release notes from merged PRs
- Prompt library — a shared collection of reusable prompts for common dev tasks
Have a different idea? Open a discussion or raise it in the team Slack.
- Low friction — tools should require minimal setup to use
- Composable — prefer small tools that do one thing well
- Shared by default — if it helps you, it probably helps someone else
- Iterative — ship early, improve together
MIT — free to use, modify, and distribute.
Maintained by the engineering team. Everyone is an author here.