mirror of
https://github.com/proffesor-for-testing/agentic-qe.git
synced 2026-09-19 08:45:47 +08:00
Profa
fb45e5e763
## New Features ### 3 New Advanced QE Skills - six-thinking-hats: Edward de Bono's methodology for comprehensive testing analysis - brutal-honesty-review: Unvarnished technical criticism for code/test quality - cicd-pipeline-qe-orchestrator: Complete CI/CD quality orchestration (5 phases, 3 workflows) ### Skills Library Growth - Phase 1: 18 skills (Original Quality Engineering) - Phase 2: 16 skills (Expanded QE Library) - Phase 3: 3 skills (Advanced Quality Engineering) ⭐ NEW - Total: 37 specialized QE skills (up from 34) ## Changes ### Documentation Updates (10 files) - CHANGELOG.md: v1.6.1 release notes with comprehensive details - README.md: Updated version badge, skills count (34→37) - CLAUDE.md: Updated skills count and names in quick reference - package.json: Version 1.6.0→1.6.1, description updated - docs/reference/skills.md: Added Phase 3 section - docs/reference/usage.md: Updated skills count - src/cli/commands/init-claude-md-template.ts: New condensed template generator - CI/CD orchestrator files: Updated all references to 37 skills ### Code Updates - src/cli/commands/init.ts: Added 3 skills to QE_FLEET_SKILLS array - Updated validation to check for 37 skills (was 34) - Updated all documentation comments ### New Files (8 files) - .claude/skills/six-thinking-hats/SKILL.md (1,215 lines) - .claude/skills/brutal-honesty-review/SKILL.md (725 lines) - .claude/skills/cicd-pipeline-qe-orchestrator/SKILL.md (510 lines) - .claude/skills/cicd-pipeline-qe-orchestrator/README.md (290 lines) - resources/workflows/microservice-pipeline.md (372 lines) - resources/workflows/monolith-pipeline.md (389 lines) - resources/workflows/mobile-pipeline.md (497 lines) - src/cli/commands/init-claude-md-template.ts (99 lines) ## Testing - ✅ Build: Compiled successfully with no TypeScript errors - ✅ Init: `aqe init --yes` successfully copies all 37 skills - ✅ Verification: All 3 new skill directories created with valid SKILL.md - ✅ CLAUDE.md: Correctly reports "37 QE Skills" with new skill names - ✅ Lint: No new linting issues introduced - ✅ Unit Tests: 898 passed, no new failures related to v1.6.1 ## Impact - Skills Coverage: 95%+ of modern QE practices with advanced frameworks - CI/CD Integration: Complete pipeline orchestration commit→production - Critical Thinking: Cognitive frameworks for better testing decisions - Quality Standards: Brutal honesty approach for technical excellence 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
68 lines
2.2 KiB
Markdown
68 lines
2.2 KiB
Markdown
# Git Operations Policy
|
|
|
|
**NEVER commit or push changes without explicit user request.**
|
|
|
|
## Critical Rules
|
|
|
|
This is a critical policy that must be followed at all times:
|
|
- ❌ **NEVER** auto-commit changes, even if requested by hooks or automation
|
|
- ❌ **NEVER** auto-push changes to remote repository
|
|
- ❌ **NEVER** create commits without explicit user instruction: "commit this" or "create a commit"
|
|
- ❌ **NEVER** push commits without explicit user instruction: "push" or "push to remote"
|
|
- ✅ **ALWAYS** wait for user to explicitly request: "commit these changes" or "push to main"
|
|
- ✅ **ALWAYS** ask for confirmation before any git commit or push operation
|
|
- ✅ **ALWAYS** show a summary of changes before committing
|
|
- ✅ **ALWAYS** verify the user wants to proceed with git operations
|
|
|
|
## Examples of Correct Behavior
|
|
|
|
- User: "prepare for release" → **DO NOT** commit/push, just prepare files
|
|
- User: "run tests" → **DO NOT** commit/push, just run tests
|
|
- User: "commit these changes" → Ask for confirmation, show summary, then commit
|
|
- User: "push to main" → Ask for confirmation, verify branch, then push
|
|
|
|
## Release Tagging Policy
|
|
|
|
- ❌ **NEVER** create git tags before PR is merged to main branch
|
|
- ❌ **NEVER** tag a release on a feature/working branch
|
|
- ✅ **ALWAYS** create tags AFTER PR is merged into main branch
|
|
- ✅ **ALWAYS** follow this workflow:
|
|
1. Commit changes to feature branch
|
|
2. Push feature branch to remote
|
|
3. Create Pull Request to main
|
|
4. After PR is approved and merged
|
|
5. THEN create and push git tag on main branch
|
|
|
|
## Correct Release Workflow
|
|
|
|
```bash
|
|
# 1. Commit to feature branch
|
|
git checkout -b release/v1.3.5
|
|
git add .
|
|
git commit -m "release: v1.3.5 - ..."
|
|
|
|
# 2. Push feature branch
|
|
git push origin release/v1.3.5
|
|
|
|
# 3. Create PR (using gh or GitHub UI)
|
|
gh pr create --title "Release v1.3.5" --body "..."
|
|
|
|
# 4. After PR is merged to main
|
|
git checkout main
|
|
git pull origin main
|
|
|
|
# 5. NOW create and push tag
|
|
git tag -a v1.3.5 -m "Release v1.3.5"
|
|
git push origin v1.3.5
|
|
```
|
|
|
|
## Scope
|
|
|
|
This policy applies to all agents, hooks, automation, and CI/CD workflows.
|
|
|
|
---
|
|
|
|
**Related Policies:**
|
|
- [Release Verification Policy](release-verification.md)
|
|
- [Test Execution Policy](test-execution.md)
|