Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
150 changes: 150 additions & 0 deletions .agents/skills/GenericAgent/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,150 @@
---
name: genericagent-conventions
description: Development conventions and patterns for GenericAgent. Python project with conventional commits.
---

# Genericagent Conventions

> Generated from [imMamdouhaboammar/GenericAgent](https://github.com/imMamdouhaboammar/GenericAgent) on 2026-08-07

## Overview

This skill teaches Claude the development patterns and conventions used in GenericAgent.

## Tech Stack

- **Primary Language**: Python
- **Architecture**: hybrid module organization
- **Test Location**: separate

## When to Use This Skill

Activate this skill when:
- Making changes to this repository
- Adding new features following established patterns
- Writing tests that match project conventions
- Creating commits with proper message format

## Commit Conventions

Follow these commit message conventions based on 6 analyzed commits.

### Commit Style: Conventional Commits

### Prefixes Used

- `test`
- `ci`

### Message Guidelines

- Average message length: ~50 characters
- Keep first line concise and descriptive
- Use imperative mood ("Add feature" not "Added feature")


*Commit message example*

```text
test(security): cover desktop bridge origin isolation
```

*Commit message example*

```text
ci: add temporary origin regression runner
```

*Commit message example*

```text
ci: run temporary origin regression on draft PR
```

*Commit message example*

```text
test: fix desktop bridge module loading in regression harness
```

*Commit message example*

```text
test(security): cover actual bridge responses and null origin
```

*Commit message example*

```text
ci: enable one-shot origin guard patch
```

## Architecture

### Project Structure: Single Package

This project uses **hybrid** module organization.

### Configuration Files

- `.github/workflows/tmp-apply-origin-guard.yml`
- `.github/workflows/tmp-desktop-bridge-origin-regression.yml`

### Guidelines

- This project uses a hybrid organization
- Follow existing patterns when adding new code

## Code Style

### Language: Python

### Naming Conventions

| Element | Convention |
|---------|------------|
| Files | kebab-case |
| Functions | camelCase |
| Classes | PascalCase |
| Constants | SCREAMING_SNAKE_CASE |

### Import Style: Relative Imports

### Export Style: Named Exports


*Preferred import style*

```typescript
// Use relative imports
import { Button } from '../components/Button'
import { useAuth } from './hooks/useAuth'
```

*Preferred export style*

```typescript
// Use named exports
export function calculateTotal() { ... }
export const TAX_RATE = 0.1
export interface Order { ... }
```

## Best Practices

Based on analysis of the codebase, follow these practices:

### Do

- Use conventional commit format (feat:, fix:, etc.)
- Use kebab-case for file names
- Prefer named exports

### Don't

- Don't write vague commit messages
- Don't deviate from established patterns without discussion

---

*This skill was auto-generated by [ECC Tools](https://ecc.tools). Review and customize as needed for your team.*
6 changes: 6 additions & 0 deletions .agents/skills/GenericAgent/agents/openai.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
interface:
display_name: "GenericAgent"
short_description: "Repo-specific patterns and workflows for GenericAgent"
default_prompt: "Use the GenericAgent repo skill to follow existing architecture, testing, and workflow conventions."
policy:
allow_implicit_invocation: true
Loading