atft-code-quality
Enforce lint, formatting, typing, testing, and security hygiene across the ATFT-GAT-FAN codebase.
Best use case
atft-code-quality is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Enforce lint, formatting, typing, testing, and security hygiene across the ATFT-GAT-FAN codebase.
Teams using atft-code-quality should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/atft-code-quality/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How atft-code-quality Compares
| Feature / Agent | atft-code-quality | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Enforce lint, formatting, typing, testing, and security hygiene across the ATFT-GAT-FAN codebase.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# ATFT Code Quality Skill ## Mission - Maintain production-readiness by catching regressions before merge or deployment. - Automate formatting, static analysis, and targeted test execution. - Surface remediation paths for failing checks with minimal GPU disruption. ## Trigger Phrases - “Run quality gate”, “lint/format the repo”, “execute tests”, “type check”, “pre-commit”. - Requests mentioning Ruff, mypy, pytest, security audit, or dependency hygiene. ## Quality Pipeline 1. **Workspace scan** - `git status --short` - `tools/project-health-check.sh --section quality` 2. **Formatting & Lint** - `ruff check src/ --fix` - `ruff format src/ tests/` 3. **Type Safety** - `mypy src/gogooku3 scripts/` - `pyright` if TypeScript integration touched. 4. **Testing Layers** - `pytest tests/unit -n auto -q` - `pytest tests/integration -m "not slow"` - `python test_short_selling.py --strict` for risk module. 5. **Security & Secrets** - `pip install bandit safety` (once) then `bandit -qr src/` - `detect-secrets scan` with baseline `security/detect-secrets.baseline`. 6. **Pre-commit Sweeps** - `pre-commit run --all-files` - `pre-commit run --hook-stage manual conventional-pre-commit`. ## Specialized Workflows ### Fast Feedback (single file change) - `ruff check src/gogooku3/<module>.py --fix`. - `pytest tests/unit/test_<module>.py -k <case>`. - `mypy src/gogooku3/<module>.py`. ### GPU-Sensitive Checks - For CUDA kernels or Torch compile edits: `pytest tests/integration/test_gpu_training.py::test_compile_path --maxfail=1`. - Validate memory usage script: `python tools/gpu_memory_report.py --dry-run`. ### Dependency Hygiene - `pip-compile requirements.in` (if edited). - `python tools/dependency_audit.py --fail-on-critical`. - Update lockfiles and note changes in `docs/ops/dependency_log.md`. ## Failure Handling - **Lint failure** → reference Ruff rule from output, fix quickly; prefer `ruff --fix-only RULE`. - **Type errors** → add precise type hints, update `mypy.ini` only with justification in docstring. - **Flaky tests** → rerun with `pytest -k test_name --lf`; mark with `@pytest.mark.flaky` only when documented in `tests/README.md`. - **Security findings** → rotate secrets, update `.env.example`, notify DevSecOps via `security/alerts.md`. ## Codex Collaboration - Launch `./tools/codex.sh "Perform deep static audit of src/gogooku3"` for architectural refactors or elusive bug hunts. - Use `codex exec --model gpt-5-codex "Review failing pytest logs and propose fixes"` when triaging stubborn CI failures. - Reflect Codex recommendations into permanent lint/type rules and note significant changes in `quality/last_quality_report.md`. ## Exit Criteria - All commands exit 0. - Updated artifacts recorded in `quality/last_quality_report.md`. - Provide summary + next steps in PR description or change log.
Related Skills
assessing-architecture-quality
Use when assessing codebase architecture and you feel pressure to soften critique, lead with strengths, or frame problems diplomatically - provides evidence-based critical assessment resisting relationship and economic pressures
architecture-quality-assess
Converted Claude skill for architecture-quality-assess. Use when Codex should run the converted architecture-quality-assess workflow.
aposd-maintaining-design-quality
Enforce strategic programming discipline when modifying existing code. Guide through STOP-ASK-DECIDE-VERIFY workflow with urgency tier assessment (trivial/minor/standard/emergency). Include when NOT to refactor (Chesterton's Fence, performance-critical, no tests) and block tactical shortcuts via anti-rationalization tables. Use when fixing bugs, extending features, or tempted to make quick fixes. Triggers on: modify code, fix bug, extend feature, quick fix, tactical change.
agentic-jumpstart-code-quality
Code quality guidelines for Jarvy CLI - Rust formatting, Clippy linting, error handling patterns, documentation standards, and Conventional Commits.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
atft-pipeline
Manage J-Quants ingestion, feature graph generation, and cache hygiene for the ATFT-GAT-FAN dataset pipeline.
51-execute-quality-150
[51] EXECUTE. Commitment to maximum quality work with 150% coverage. Use when you need the highest quality output for critical tasks, complex problems, important decisions, or when standard work isn't enough. Triggers on "maximum quality", "150% mode", "full quality", "critical task", or when you explicitly want AI to work at its best.
ai-content-quality-checker
AI生成コンテンツの総合品質チェックスキル。読みやすさ、正確性、関連性、独自性、SEO、アクセシビリティ、エンゲージメント、文法・スタイルを多角的に評価。
1k-code-quality
Code quality standards for OneKey. Use when fixing lint warnings, running pre-commit tasks, handling unused variables, writing comments, or ensuring code quality. All comments must be in English. Triggers on lint, linting, eslint, oxlint, tsc, type check, unused variable, comment, documentation, spellcheck, code quality, pre-commit, yarn lint.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
quality-nonconformance
Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing.
Data Quality Monitoring
Data Quality (DQ) Monitoring is the continuous process of validating data against predefined rules and expectations. In a modern data stack, monitoring must happen at every stage: **Ingestion**, **Tra