Agent skill · writing content · jeremylongshore
improve
Analyses the current project across code quality, feature gaps, documentation, security, competitive landscape, and monetisation opportunities, then files prioritised GitHub issues. Use when the user says improve this, analyse this project, find improvements, or fill the backlog.
Why this skill is useful
Adds a comprehensive analysis script that generates actionable GitHub issues based on multiple project dimensions, which the AI cannot generate on its own.
What it needs
Requires bash, gh installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Improve Project: !basename $(git rev-parse --show-toplevel 2>/dev/null) 2>/dev/null basename $PWD Open issues: !gh issue list --state open --json number --jq 'length' 2>/dev/null echo "unknown" Last tag: !git describe --tags --abbrev=0 2>/dev/null echo "none" Recent commits: !git log --oneline -5 2>/dev/null echo "none" Analyses the current project from multiple angles — technical, strategic, and commercial — then files actionable GitHub issues for every finding. Step 0: Pre-flight check Step 1: Understand the project Read these files to build context before analysing anything: README.md — stated purpose, audience, and feature set CLAUDE.md — current status, decisions, next steps Any .claude-plugin/plugin.json or manifest files — metadata and versioning Then inventory all files: Read a representative sample of source files to understand the implementation. Note: what does this project do, who is it for, and what problem does it solve? Step 2: Code quality and bugs Review source files for: Logic errors, edge cases, or fragile assumptions Anti-patterns or code that will break under realistic conditions Inconsistent behaviour between similar components Missing error handling at system boundaries (user input, external APIs) Unnecessary complexity or premature abstraction Hardcoded values that should be configurable For shell scripts, also check: Label findings: bug for defects, enhancement for quality improvements. Step 3: Feature completeness Based on the project's stated purpose in README.md, identify: Features described but not yet implemented Obvious gaps a user of this tool would expect Incomplete workflows (things that almost work end-to-end but don't) Integration opportunities with tools this project already touches Label findings: enhancement. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/improve