Skip to main content
command CX Codex

audit-project-github — Claude Code command

The audit-project-github command for Claude Code turns deferred /audit-project findings into GitHub issues via gh, keeping security findings out of the public tracker. It requires git and authenticated gh.

MIT ★ 2,003 updated 2026-07-26

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add composio-community/awesome-claude-plugins
/plugin install audit-project@awesome-claude-plugins
Open on GitHub

What audit-project-github does

This is the GitHub phase of /audit-project. Before anything gets filed, the command checks for git, checks for gh, and looks at whether origin points to github.com. One failed check and no issues are created. Each issue carries severity, category, an effort estimate, the current behavior in a code block, a proposed fix, the impact and the files involved.

Exposed credentials, authorization holes and injection flaws never become public issues. They get fixed on the spot when possible, kept in internal notes, and the report mentions them without detail. An authenticated gh plus a github.com remote is the hard precondition: without both, nothing is filed and TECHNICAL_DEBT.md stays where it is.

After that the file is deleted and the removal committed, provided git is there, gh is authenticated, the remote is GitHub and every non-security issue exists. Passing --create-tech-debt or leaving security findings behind keeps the file in the repo. If issues were created, a final commit lists their numbers.

What it helps with

  • file deferred audit findings as GitHub issues
  • keep security findings out of the public tracker
  • delete TECHNICAL_DEBT.md once tasks live in the tracker
  • format an issue with severity, category and affected files
  • close an audit session with one commit listing issue numbers

Example prompts for the agent

  • Run /audit-project-github on this repo and open issues for the deferred items.
  • Keep the security findings internal and file everything else through gh.
  • Drop TECHNICAL_DEBT.md now that every task is tracked in GitHub.

How to install audit-project-github

1Plugin marketplace

/plugin marketplace add composio-community/awesome-claude-plugins
/plugin install audit-project@awesome-claude-plugins

2Manually: put the files in place

.claude/commands/audit-project-github.md

Call it with /audit-project-github. For all projects use ~/.claude/commands/

Questions about audit-project-github

How do I install audit-project-github in Claude Code?

Through the plugin marketplace: run /plugin marketplace add composio-community/awesome-claude-plugins, then /plugin install audit-project@awesome-claude-plugins.

What does audit-project-github do?

It takes the deferred items from /audit-project and opens GitHub issues for them with gh issue create, then cleans up TECHNICAL_DEBT.md once tracking moved to GitHub. Security findings stay internal.

When is TECHNICAL_DEBT.md kept?

When GitHub access is missing, gh is not authenticated, the --create-tech-debt flag was passed, or security findings remain. The file is left in the repository in all those cases.

Source text

audit-project-github.md · MIT
# Phase 8: GitHub Issue Creation - Reference

This file contains GitHub integration for `/audit-project`.

**Parent document**: `audit-project.md`

## Pre-Conditions

```bash
# Check if git and gh are available
GIT_AVAILABLE=$(command -v git >/dev/null 2>&1 && echo "true" || echo "false")
GH_AVAILABLE=$(command -v gh >/dev/null 2>&1 && echo "true" || echo "false")

# Check if this is a GitHub repository
IS_GITHUB_REPO="false"
if [ "$GIT_AVAILABLE" = "true" ]; then
  REMOTE_URL=$(git remote get-url origin 2>/dev/null || echo "")
  if echo "$REMOTE_URL" | grep -q "github.com"; then
    IS_GITHUB_REPO="true"
  fi
fi
```

## Creating GitHub Issues

If `git` and `gh` are available, create issues for **non-security** deferred items:

```bash
if [ "$GH_AVAILABLE" = "true" ] && [ "$IS_GITHUB_REPO" = "true" ]; then
  echo "Creating GitHub issues for deferred items..."

  # DO NOT create public issues for security-sensitive findings
  for issue in "${DEFERRED_NON_SECURITY_ISSUES[@]}"; do
    gh issue create \
      --title "${issue.title}" \
      --body "${issue.body}"
  done

  echo "Created ${#DEFERRED_NON_SECURITY_ISSUES[@]} GitHub issues"
fi
```

## Issue Format

Each created issue includes:

```markdown
## Issue from /audit-project

**Severity**: [Critical|High|Medium|Low]
**Category**: [Performance|Architecture|Code Quality|Enhancement]
**Effort**: [Small|Medium|Large] (~X hours)

### Description
[Description of the issue]

### Current Behavior
\`\`\`[language]
[Code showing the problem]
\`\`\`

### Proposed Fix
[Specific remediation approach]

### Impact
[Why this matters]

### Files
- [List of affected files]
```

## Security Issue Handling

```

  [WARN] SECURITY ISSUES MUST NOT BE PUBLIC

  The following must NOT be created as GitHub issues:
  - Token/credential exposure
  - Authentication vulnerabilities
  - Authorization bypasses
  - Injection vulnerabilities
  - Any exploitable security finding

  For security issues:
  1. Fix immediately if possible
  2. Keep documented internally only
  3. Note in completion report (no details)

```

## TECHNICAL_DEBT.md Cleanup

After all issues are handled, remove TECHNICAL_DEBT.md:

```bash
if [ "$GH_AVAILABLE" = "true" ] && [ "$IS_GITHUB_REPO" = "true" ]; then
  if [ -f "TECHNICAL_DEBT.md" ]; then
    rm TECHNICAL_DEBT.md
    git add TECHNICAL_DEBT.md
    git commit -m "chore: remove TECHNICAL_DEBT.md - issues tracked in GitHub

Created GitHub issues for all deferred non-security items.
Security-sensitive issues kept internal."
    echo "Removed TECHNICAL_DEBT.md - issues now in GitHub"
  fi
else
  echo "TECHNICAL_DEBT.md retained - no GitHub integration"
fi
```

## Cleanup Conditions

**Remove TECHNICAL_DEBT.md when ALL true:**
1. `git` is available
2. `gh` CLI is available and authenticated
3. Repository has GitHub remote
4. All non-security issues created as GitHub issues

**Keep TECHNICAL_DEBT.md when ANY true:**
1. No GitHub integration available
2. `gh` CLI not authenticated
3. User requested `--create-tech-debt` flag
4. Security issues exist

## Final Commit

If issues were created:

```bash
git add -A
git commit -m "chore: audit-project complete - issues tracked in GitHub

Created X GitHub issues for deferred items:
- #N: [issue title]
- #N: [issue title]

Security-sensitive issues (Y total) kept internal.
Fixed Z issues in this review session."
```

© Community · MIT · composio-community/awesome-claude-plugins

Similar slash commands

All slash commands for Code review and refactoring →

From the same set68

The whole set →
report report is a Claude Code command that shows skill-bus subscription matches, condition skips, and skills without subscriptions to help find coverage gaps. CX Codex +1 ★ 2,003repo stars complete A signal command: Claude runs it by itself once a skill with "when": "complete" subscriptions has finished, and a hook starts the next steps in the chain. CX Codex +1 ★ 2,003repo stars reflecting-on-sessions reflecting-on-sessions inspects skill-bus telemetry across task transitions to surface unhandled skill calls and rule gaps. CX Codex +1 ★ 2,003repo stars remove-sub remove-sub is a Claude Code command for managing skill-event subscriptions by scope: remove project triggers, disable global ones for a project, or restore them. CX Codex +1 ★ 2,003repo stars edit-insert edit-insert modifies stored text content and trigger conditions for skill-bus inserts. Useful when you need to update prompt context across all connected subscriptions. CX Codex +1 ★ 2,003repo stars ship-error-handling The ship-error-handling command documents how to recover /ship from CI failures, merge conflicts, deployment errors, and other shipping problems. CX Codex +1 ★ 2,003repo stars backend-architect backend-architect — a subagent for designing APIs, server-side logic, databases, and scalable backend systems. CX Codex ★ 2,003repo stars frontend-developer The frontend-developer subagent for Claude Code builds responsive components in React, Vue, or Angular and tunes frontend rendering performance. CX Codex ★ 2,003repo stars

Project sponsors

Companies that keep this analytics open