{
  "markdown": "# Claude DevTools\n\nA comprehensive collection of skills and commands for enforcing quality gates in software development with Claude Code.\n\n## Overview\n\nThis repository provides Claude Code with systematic workflows for implementing features with proper quality assurance. Every code change goes through mandatory quality gates:\n\n1. **Testing** - Write and run tests\n2. **Linting** - Check code style and quality\n3. **Security** - Scan for vulnerabilities\n\n## Quick Start\n\n### Installation\n\n1. Clone this repository:\n```bash\ngit clone https://github.com/hitoshura25/claude-devtools.git ~/.claude-devtools\n```\n\n2. Run the installer:\n```bash\ncd ~/.claude-devtools\nchmod +x install.sh\n./install.sh\n```\n\n   This installs skills and commands **globally** - they work in ALL projects!\n\n   **Options:**\n   - Default (symlinks): Updates auto-propagate with `git pull`\n   - `./install.sh --copy`: Independent installation (won't auto-update)\n\n3. Restart Claude Code or start a new session\n\n### Usage\n\nIn Claude Code, use these commands:\n\nCommands work in **all projects** automatically:\n\n**Create a specification for a feature:**\n```\n/devtools:spec \"Plan user authentication system with JWT\"\n```\n\n**Implement a feature with full quality gates:**\n```\n/devtools:develop \"Add user authentication with JWT\"\n```\n\n**Run quality checks on existing code:**\n```\n/devtools:validate\n```\n\n**Just run tests:**\n```\n/devtools:test\n```\n\n**Just run linting:**\n```\n/devtools:lint\n```\n\n**Just run security scans:**\n```\n/devtools:security\n```\n\n**Setup PyPI publishing:**\n```\n/devtools:setup-pypi\n```\n\n**Setup npm publishing:**\n```\n/devtools:setup-npm\n```\n\n**Why `/devtools:` prefix?**\nPrevents name conflicts - you can still have your own `/test` command!\n\n## Skills\n\n### Planning & Specification\n\n- **`spec-creation`** - Create specification documents in `./specs/` for context retention across sessions\n\n### Quality Gates (Granular)\n\nThese skills handle individual quality checks:\n\n- **`testing-setup`** - Configure test framework if not already setup\n- **`testing-tdd`** - Write tests, run them, fix failures\n- **`linting-setup`** - Configure linter if not already setup\n- **`linting-check`** - Run linter, fix issues\n- **`security-setup`** - Configure security tools if not already setup\n- **`security-check`** - Run security scans, address findings\n\n### Orchestration\n\n- **`feature-development`** - Master workflow that runs all quality gates in sequence (includes spec creation)\n\n### Workflow Generation\n\n- **`pypi-publishing`** - Setup automated PyPI publishing with GitHub Actions\n- **`npm-publishing`** - Setup automated npm publishing with GitHub Actions\n\n### Android Release & Publishing\n\nComprehensive Android app release and Play Store deployment:\n\n- **`android-release-build-setup`** - Complete release build configuration (keystores, ProGuard, signing)\n- **`android-e2e-testing-setup`** - End-to-end testing with Espresso\n- **`android-release-validation`** - Validate release builds before publishing\n- **`android-playstore-setup`** - Google Play Console integration\n- **`android-playstore-publishing`** - GitHub Actions workflow for Play Store deployment\n- **`android-playstore-pipeline`** - Complete end-to-end setup in one command\n\n## How It Works\n\nWhen you run `/devtools:develop \"feature description\"`, Claude:\n\n0. **Assesses complexity** → Creates spec in `./specs/` if needed (spec-creation)\n1. **Implements the feature** according to your specification\n2. **Checks if tests exist** → Sets up test framework if needed (testing-setup)\n3. **Writes tests** → Runs them → Fixes failures (testing-tdd)\n4. **Checks if linter exists** → Sets up linter if needed (linting-setup)\n5. **Runs linter** → Fixes issues (linting-check)\n6. **Checks if security tools exist** → Sets up tools if needed (security-setup)\n7. **Runs security scans** → Addresses findings (security-check)\n8. **Updates spec** with completion status (if spec was created)\n9. **Reports completion** only when ALL gates pass\n\n**Spec Creation:** Claude intelligently decides when to create a spec based on complexity. You can explicitly request or decline with:\n- `/devtools:develop \"feature (create spec)\"` - Always creates spec\n- `/devtools:develop \"feature (no spec)\"` - Never creates spec\n- `/devtools:develop \"feature\"` - AI decides based on complexity\n\n## Supported Languages\n\n- **TypeScript/JavaScript** - Jest/Vitest, ESLint, Prettier, Semgrep, npm audit\n- **Python** - pytest, Ruff/Pylint, Semgrep, pip-audit, bandit\n- **Kotlin/Android** - JUnit, ktlint, Detekt, Semgrep, OWASP Dependency-Check\n\n## Commands Reference\n\n### `/devtools:spec`\n\nCreate a specification document for a feature without implementing it.\n\n**Usage:**\n```\n/devtools:spec \"Plan user authentication system\"\n/devtools:spec \"Design API for payment processing\"\n```\n\n**What it does:**\n- Analyzes feature requirements\n- Explores codebase for context\n- Creates spec file in `./specs/YYYY-MM-DD-feature-name.md`\n- Chooses appropriate detail level (1, 2, or 3)\n- Enables session resumption for complex work\n\n### `/devtools:develop`\n\nImplement a feature with complete quality gates.\n\n**Usage:**\n```\n/devtools:develop \"Add password reset functionality\"\n/devtools:develop \"Fix bug where users can't upload images\"\n/devtools:develop \"Refactor authentication module (create spec)\"\n/devtools:develop \"Simple typo fix (no spec)\"\n```\n\n**What it does:**\n- Assesses complexity and creates spec if needed\n- Implements the feature\n- Sets up testing/linting/security if needed\n- Writes and runs tests\n- Runs linting and fixes issues\n- Runs security scans\n- Updates spec with completion status\n- Only completes when all gates pass\n\n**Spec control:**\n- Add `(create spec)` to force spec creation\n- Add `(no spec)` to skip spec creation\n- Omit for AI to decide based on complexity\n\n### `/devtools:validate`\n\nRun all quality gates on existing code without implementing new features.\n\n**Usage:**\n```\n/devtools:validate\n```\n\n**What it does:**\n- Runs tests (sets up if needed)\n- Runs linting (sets up if needed)\n- Runs security scans (sets up if needed)\n- Reports all issues found\n\n### `/devtools:test`\n\nFocus on testing only.\n\n**Usage:**\n```\n/devtools:test \"the authentication module\"\n/devtools:test\n```\n\n**What it does:**\n- Sets up test framework if needed\n- Writes/updates tests\n- Runs tests until all pass\n\n### `/devtools:lint`\n\nFocus on linting only.\n\n**Usage:**\n```\n/devtools:lint\n```\n\n**What it does:**\n- Sets up linter if needed\n- Runs linting checks\n- Auto-fixes what's possible\n- Reports remaining issues\n\n### `/devtools:security`\n\nFocus on security scanning only.\n\n**Usage:**\n```\n/devtools:security\n```\n\n**What it does:**\n- Sets up security tools if needed\n- Runs Semgrep (static analysis)\n- Runs OSV-Scanner (dependency vulnerabilities)\n- Reports all security findings\n\n### `/devtools:setup-pypi`\n\nSetup automated PyPI publishing workflow for Python projects.\n\n**Usage:**\n```\n/devtools:setup-pypi\n```\n\n**What it does:**\n- Gathers project information (package name, author, etc.)\n- Creates pyproject.toml and setup.py if needed\n- Generates 3 GitHub Actions workflows (release, PR testing, reusable)\n- Creates version calculation script\n- Provides instructions for PyPI Trusted Publishers setup\n\n**Features:**\n- PyPI Trusted Publishers (no API tokens needed)\n- Automatic versioning with setuptools_scm\n- TestPyPI publishing for pull requests\n- Fail-safe tag creation (only after successful publish)\n\n### `/devtools:setup-npm`\n\nSetup automated npm publishing workflow for TypeScript/JavaScript packages.\n\n**Usage:**\n```\n/devtools:setup-npm\n```\n\n**What it does:**\n- Reads package.json for package information\n- Supports monorepos with package-specific paths\n- Generates GitHub Actions workflow\n- Provides instructions for NPM_TOKEN setup\n\n**Features:**\n- Automatic publishing on push to main\n- RC (release candidate) versions for pull requests\n- Monorepo support with path-based triggers\n- Automatic version bumping\n\n### `/devtools:android-release-setup`\n\nSetup complete Android release build configuration with dual keystore strategy.\n\n**Usage:**\n```\n/devtools:android-release-setup\n```\n\n**What it does:**\n- Analyzes Android project structure\n- Generates production keystore (CI/CD only)\n- Generates local development keystore\n- Configures ProGuard/R8 minification\n- Updates build.gradle.kts with signing config\n- Creates gradle.properties.template\n- Updates .gitignore for security\n\n**Features:**\n- Dual keystore strategy (production + local dev)\n- Auto-generated secure passwords\n- Base64 encoding for GitHub Secrets\n- ProGuard safe defaults with library-specific rules\n- Dual-source credentials (env vars + gradle.properties)\n- Comprehensive security warnings and documentation\n\n## Configuration\n\n### Project-Specific Commands\n\nYou can customize commands per project by editing `.claude/commands.json`:\n\n```json\n{\n  \"commands\": [\n    {\n      \"name\": \"develop\",\n      \"description\": \"Custom develop workflow\",\n      \"prompt\": \"Follow /Users/vinayakmenon/claude-devtools/skills/feature-development/SKILL.md but skip security checks for now\"\n    }\n  ]\n}\n```\n\n### Skill Customization\n\nSkills are just markdown files. You can:\n- Fork and modify for your needs\n- Add project-specific requirements\n- Adjust quality thresholds\n\n## Architecture\n\n```\nclaude-devtools/\n├── skills/                    # The intelligence\n│   ├── testing-setup/        # Setup test framework\n│   ├── testing-tdd/          # Write and run tests\n│   ├── linting-setup/        # Setup linter\n│   ├── linting-check/        # Run linting\n│   ├── security-setup/       # Setup security tools\n│   ├── security-check/       # Run security scans\n│   ├── feature-development/  # Orchestrates all gates\n│   ├── pypi-publishing/      # PyPI workflow generation\n│   │   └── templates/        # Workflow templates\n│   └── npm-publishing/       # npm workflow generation\n│       └── templates/        # Workflow templates\n│\n├── commands/                  # Claude Code commands\n│   └── commands.json         # Command definitions\n│\n└── configs/                   # Reusable configurations (future)\n    ├── semgrep/              # Security rules\n    ├── eslint/               # Linting rules\n    └── jest/                 # Test configs\n```\n\n## Why This Approach?\n\n**Skills over CLI:**\n- No dependencies to install\n- Works across all languages\n- Transparent - you can read what Claude will do\n- Easy to customize per project\n\n**Granular skills over monolithic:**\n- Reusable components\n- Can run individually (/test, /lint, /security)\n- Easy to debug when something fails\n- Can compose into different workflows\n\n**Mandatory quality gates:**\n- Catches bugs early\n- Prevents security vulnerabilities\n- Maintains code quality\n- No shortcuts - quality is enforced\n\n## Best Practices\n\n1. **Always use `/develop` for new features** - ensures quality gates run\n2. **Run `/validate` before pushing** - catches issues locally\n3. **Don't skip security scans** - critical/high findings must be addressed\n4. **Document exceptions** - if you disable a rule, explain why\n5. **Keep tools updated** - regular updates catch new vulnerabilities\n\n## Troubleshooting\n\n**Skills not found:**\n```bash\n# Check symlink exists\nls -la ~/.config/claude-code/skills/user/devtools\n\n# Recreate if needed\nln -s ~/.claude-devtools/skills ~/.config/claude-code/skills/user/devtools\n```\n\n**Commands not working:**\n```bash\n# Ensure commands.json exists in project\nls .claude/commands.json\n\n# Copy from template\ncp ~/.claude-devtools/commands/commands.json .claude/\n```\n\n**Quality gates taking too long:**\n- Consider running only changed files for linting\n- Use test filtering for large test suites\n- Configure security tool exclusions\n\n## Roadmap\n\n### Phase 1 (Complete)\n- ✅ Core quality gate skills (testing, linting, security)\n- ✅ Feature development orchestration\n- ✅ Claude Code commands\n\n### Phase 2 (Complete)\n- ✅ Workflow generation skills (PyPI, npm)\n- ✅ PyPI Trusted Publishers support\n- ✅ npm monorepo support\n\n### Phase 3 (Complete) ✅\n- ✅ Android Play Store deployment workflows\n- ✅ Skills architecture refactoring\n- ✅ Atomic skills decomposition\n- ✅ ~95% reliability per skill\n\n### Phase 4 (Future)\n- [ ] Project scaffolding templates\n- [ ] Reusable config files\n- [ ] CI/CD integration helpers\n- [ ] Pre-commit hook generation\n- [ ] Quality metrics tracking\n\n## Contributing\n\nContributions welcome! Please:\n1. Follow existing skill format\n2. Test skills on real projects\n3. Document any new patterns\n4. Submit PR with clear description\n\n## License\n\nApache-2.0\n\n## Author\n\nVinayak Menon\n\n## Links\n\n- **Repository**: https://github.com/hitoshura25/claude-devtools\n- **Issues**: https://github.com/hitoshura25/claude-devtools/issues\n",
  "bytes": 12672,
  "sha": "c55654241dc6dccb4080db0fd7310bea051854d92ca5cf54d3764d16476abe38",
  "repo_slug": "hitoshura25/claude-devtools",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_hitoshura25_claude_devtools_425bcfac/readme"
}