Phase/8

.agents/skills/codebadger/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: codebadger-conventions
+description: Development conventions and patterns for codebadger. Python project with mixed commits.
+---
+
+# Codebadger Conventions
+
+> Generated from [NguyenThanhHungDev140503/codebadger](https://github.com/NguyenThanhHungDev140503/codebadger) on 2026-08-11
+
+## Overview
+
+This skill teaches Claude the development patterns and conventions used in codebadger.
+
+## Tech Stack
+
+- **Primary Language**: Python
+- **Architecture**: type-based 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 13 analyzed commits.
+
+### Commit Style: Mixed Style
+
+### Prefixes Used
+
+- `docs`
+- `feat`
+
+### Message Guidelines
+
+- Average message length: ~42 characters
+- Keep first line concise and descriptive
+- Use imperative mood ("Add feature" not "Added feature")
+
+
+*Commit message example*
+
+```text
+feat(05-01): implement project version contract and credential store
+```
+
+*Commit message example*
+
+```text
+docs(05-01): complete project version contract plan
+```
+
+*Commit message example*
+
+```text
+feat(05-02): implement safe git sync adapter and version promotion
+```
+
+*Commit message example*
+
+```text
+docs(05-02): complete git sync and version promotion plan with secret-safe headers
+```
+
+*Commit message example*
+
+```text
+docs(05): mark phase 05 complete
+```
+
+*Commit message example*
+
+```text
+docs(06): capture phase context
+```
+
+*Commit message example*
+
+```text
+docs(state): record phase 6 context session
+```
+
+*Commit message example*
+
+```text
+fix git sync service
+```
+
+## Architecture
+
+### Project Structure: Single Package
+
+This project uses **type-based** module organization.
+
+### Source Layout
+
+```
+src/
+├── api/
+├── services/
+├── tools/
+├── utils/
+```
+
+### Configuration Files
+
+- `.github/workflows/deploy-vps.yml`
+
+### Guidelines
+
+- Group code by type (components, services, utils)
+- Keep related functionality in the same type folder
+- Avoid circular dependencies between type folders
+
+## Code Style
+
+### Language: Python
+
+### Naming Conventions
+
+| Element | Convention |
+|---------|------------|
+| Files | snake_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 { ... }
+```
+
+## Testing
+
+### Test Framework
+
+No specific test framework detected — use the repository's existing test patterns.
+
+### File Pattern: `*.test.ts`
+
+### Test Types
+
+- **Unit tests**: Test individual functions and components in isolation
+
+
+## Common Workflows
+
+These workflows were detected from analyzing commit patterns.
+
+### Feature Development
+
+Standard feature implementation workflow
+
+**Frequency**: ~12 times per month
+
+**Steps**:
+1. Add feature implementation
+2. Add tests for feature
+3. Update documentation
+
+**Files typically involved**:
+- `**/*.test.*`
+- `**/api/**`
+
+**Example commit sequence**:
+```
+feat(05-01): implement project version contract and credential store
+docs(05-01): complete project version contract plan
+feat(05-02): implement safe git sync adapter and version promotion
+```
+
+
+## Best Practices
+
+Based on analysis of the codebase, follow these practices:
+
+### Do
+
+- Follow *.test.ts naming pattern
+- Use snake_case for file names
+- Prefer named exports
+
+### Don't
+
+- Don't skip tests for new features
+- 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.*

.agents/skills/codebadger/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Codebadger"
+  short_description: "Repo-specific patterns and workflows for codebadger"
+  default_prompt: "Use the codebadger repo skill to follow existing architecture, testing, and workflow conventions."
+policy:
+  allow_implicit_invocation: true

.claude/commands/feature-development.md

@@ -0,0 +1,36 @@
+---
+name: feature-development
+description: Workflow command scaffold for feature-development in codebadger.
+allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
+---
+
+# /feature-development
+
+Use this workflow when working on **feature-development** in `codebadger`.
+
+## Goal
+
+Standard feature implementation workflow
+
+## Common Files
+
+- `**/*.test.*`
+- `**/api/**`
+
+## Suggested Sequence
+
+1. Understand the current state and failure mode before editing.
+2. Make the smallest coherent change that satisfies the workflow goal.
+3. Run the most relevant verification for touched files.
+4. Summarize what changed and what still needs review.
+
+## Typical Commit Signals
+
+- Add feature implementation
+- Add tests for feature
+- Update documentation
+
+## Notes
+
+- Treat this as a scaffold, not a hard-coded script.
+- Update the command if the workflow evolves materially.