Craftsman Marketplace banner
gul-labs gul-labs

Craftsman Marketplace

AI community

Description

Engineering-readiness audits for AI-built apps. A Claude Code and Codex plugin that finds production risks across ten domains—with plain-language findings and verified fixes.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

craftsman

![Craftsman inspecting a software system for production risks](./plugins/craftsman/assets/craftsman-github-hero.png)

**The engineering review you'd get from the technical co-founder you don't have.**

You built a real app without being an engineer. It works. You're about to let real users in, maybe take payments, maybe hold their data. Most people in that position could not say what a senior engineer would flag. That gap doesn't show up until something breaks in front of a customer.

`craft-audit` is that review. Point it at your project and it audits the whole thing for production-readiness, not just one file or one pull request: it works out what your project actually is, then finds the gaps between a working demo and something you'd trust with real customers. It writes everything it finds to disk so you can pick it back up later instead of losing the work.

Written by [Atif Gul](https://github.com/atifgul99), a software engineer of 25 years, including time at Microsoft and Amazon.

In short

It's free and MIT licensed. It runs inside your own Claude Code or Codex session and collects no telemetry (see [SECURITY.md](./SECURITY.md)). The plugin does not send your project files or audit findings to Craftsman. Its review guidance is bundled locally; `craft-audit` only reads your code. The writes it makes are a new local folder, `.craftsman/`, holding its notes, and a line in your project's `.gitignore` (the file that tells git which files to skip) so that folder stays out of version control. If your project doesn't have a `.gitignore` yet, it creates one with that line; if it does, it just appends the line. Nothing in your app's own code changes unless you separately ask `craft-fix`, and it asks for your sign-off before it touches anything. Expect under an hour for a typical single-app audit. It applies the same standard every time, to every project you point it at, instead of a slightly different one each run.

Is this for you

You shipped someth