git-repository-workflow
Provides Git repository workflow guidelines including branch management, testing practices (TDD), Docker environment handling, and PR workflow. Use this skill when implementing features, fixing bugs, or making any code changes in a Git repository.
What this skill does
# Git Repository Workflow
## Instructions
### CRITICAL: Never Push to Default Branches
**PROHIBITED**: `git push origin main/develop/master`
ALL changes must go through Pull Requests. No exceptions.
### Workflow Decision
```
Start Implementation
↓
Existing PR? → YES → gh pr checkout <PR#> → git pull → Implement → Push
↓ NO
User says "current branch"? → YES → Implement directly
↓ NO
git checkout main && git pull → git checkout -b feature/name → Implement
```
### Branch Naming
- `feature/` - New features
- `fix/` - Bug fixes
- `refactor/` - Code refactoring
- `docs/` - Documentation
### Testing Requirements
#### Check Test Necessity First
Before writing tests, verify if tests are required:
1. Check CLAUDE.md for test configuration (e.g., "no tests required", "skip tests")
2. If no existing tests in project and unclear, ask user: "This project has no tests. Should I add tests?"
3. If tests not required, proceed to next step without testing
#### Test-Driven Approach (When Tests Required)
Follow Red-Green-Refactor cycle:
1. **Test Skeleton First**: Define test structure before implementation
2. **Descriptive Names**: `should return 404 when user not found` (not `test1`)
3. **Test Coverage**: Happy path → Edge cases → Error cases
#### Docker Environment
When running tests, lint, or other commands in Docker projects:
```
Check if container is running → docker ps | grep <container>
↓
Running? → YES → docker exec <container> <command>
↓ NO
Start container first or run locally
```
### Web Application Testing
For E2E tests or browser automation, see [web-app-testing.md](web-app-testing.md).
### DO / DON'T
**DO**: Pull latest before starting, use descriptive branch names, verify test requirements, check Docker container status
**DON'T**: Push to main directly, create new branch for existing PR, add tests to test-free projects without confirmation, run commands outside container when app runs in Docker
## Examples
### New Feature Branch
```bash
git checkout main && git pull origin main
git checkout -b feature/descriptive-name
```
### Existing PR
```bash
gh pr checkout <PR-number>
git pull origin <branch-name>
# Make changes
git push origin <branch-name>
```
### Test Skeleton
```typescript
describe('UserAuthentication', () => {
describe('login', () => {
it('should successfully login with valid credentials', () => {});
it('should reject invalid credentials', () => {});
it('should lock account after multiple failed attempts', () => {});
});
});
```
### Docker Command Execution
```bash
# Check container status
docker ps | grep myapp
# Execute in running container
docker exec myapp-web npm test
docker exec myapp-web npm run lint
```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.