Civil Service

Prepare for Chinese civil service exams with essays and mock interviews. Use when practicing 申论, reviewing 行测 techniques, or analyzing past papers.

Security Scan

The package claims to be a Civil Service exam helper, and the included scripts mostly match that purpose, but the SKILL.md contains a mismatched developer-CLI description (init/build/deploy) which is an incoherent and unexplained discrepancy.

Purpose & Capability

Name/description and the shipped scripts (scripts/civil.sh, scripts/script.sh) implement a civil service exam helper (quizzes, essay frameworks, timers, local history/logging). However SKILL.md's main body begins with a completely different description — a 'Developer workflow automation tool' offering init/build/deploy/config commands — which is unrelated to exam prep. This mismatch between declared purpose and the documentation/content is unexpected and unexplained.

Instruction Scope

Runtime instructions and the scripts operate locally and are limited to showing exercises and logging activity, which is fine; but SKILL.md also documents developer-CLI commands (init, build, deploy, config) that imply broader filesystem/project control that the included scripts do not implement. The SKILL.md directs storing operational data under ~/.local/share/civil-service and mentions a history.log/config.json — the shipped scripts do indeed write history.jsonl and civil-service.log to that directory. No instructions call external network endpoints, but the contradictory CLI documentation is scope-creeping and may mislead users about capabilities.

Install Mechanism

No install spec or external downloads. The skill is instruction-plus-included shell scripts; nothing in the manifest pulls code from remote URLs or installs packages. That is proportionate and lower-risk compared with remote installers.

Credentials

The skill requests no environment variables or credentials. It reads HOME (to build a data dir) and allows overriding via CIVIL_SERVICE_DIR (documented). Scripts create and write files under the user's data directory but do not request secrets or unrelated credentials.

Persistence & Privilege

The scripts persist user data in ~/.local/share/civil-service (history.jsonl and civil-service.log) and create that directory. This is expected for a local helper but is persistent: users should expect entries saved on disk. The skill is not always-enabled and does not modify other skills or system-wide agent settings.

What to consider before installing

There is an unexplained mismatch: SKILL.md contains documentation for a generic developer CLI (init/build/deploy) while the actual scripts implement a Civil Service exam helper. Before installing, ask the author (or check the repo) why the documentation diverges. Inspect the included scripts yourself to confirm they do only local tasks (they write logs/history to ~/.local/share/civil-service but do not make network calls or request credentials). If you don't want persistent files, run the scripts in a sandbox or set CIVIL_SERVICE_DIR to a temporary location. Avoid installing until the doc mismatch is resolved if you need assurance the skill's behavior matches its description.

Developer workflow automation tool for project lifecycle management. Provides commands for initializing projects, running checks, building, testing, deploying, managing configuration, generating templates, producing documentation, and cleaning build artifacts — all from a single CLI interface.

Commands

Command	Description
civil-service init	Initialize a new project in the current working directory
civil-service check	Run lint, type-check, and test passes against the project
civil-service build	Build the project artifacts
civil-service test	Execute the full test suite
civil-service deploy	Show the deployment pipeline guide (build → test → stage → prod)
civil-service config	Display or manage project configuration (config.json)
civil-service status	Check overall project health and status
civil-service template <name>	Generate a code template for the given component name
civil-service docs	Generate project documentation
civil-service clean	Remove build artifacts and temporary files
civil-service help	Show the built-in help message with all commands
civil-service version	Print the current version (v2.0.0)

Data Storage

All operational data is stored in ~/.local/share/civil-service/ by default. You can override this by setting the CIVIL_SERVICE_DIR environment variable. Key files inside the data directory:

• history.log — timestamped log of every command executed
• config.json — project-level configuration (managed via config command)

The tool respects XDG_DATA_HOME if set, falling back to $HOME/.local/share.

Requirements

• Bash 4.0+ (uses set -euo pipefail for strict error handling)
• coreutils (standard date, mkdir, echo)
• No external dependencies or API keys required
• Works on Linux and macOS out of the box

When to Use

1. Bootstrapping a new project — run civil-service init to set up project scaffolding quickly from the terminal without remembering per-tool init commands
2. Pre-commit quality gates — use civil-service check as part of a Git pre-commit hook to run lint + type-check + tests before every commit
3. CI/CD pipeline steps — chain civil-service build and civil-service test inside your continuous integration scripts for a consistent, tool-agnostic interface
4. Deployment checklists — run civil-service deploy to get a guided walkthrough of the build → test → stage → prod pipeline so nothing gets skipped
5. Housekeeping and cleanup — execute civil-service clean to wipe build artifacts after releases, freeing disk space and resetting state

Examples

# Initialize a new project in the current directory
civil-service init

# Run all quality checks (lint + type-check + tests)
civil-service check

# Build the project
civil-service build

# Run the test suite
civil-service test

# View the deployment guide
civil-service deploy

# Generate a code template for a component called "auth"
civil-service template auth

# Generate project documentation
civil-service docs

# Check project health
civil-service status

# Clean up build artifacts
civil-service clean

# Show version
civil-service version

Configuration

Set the CIVIL_SERVICE_DIR environment variable to change the data directory:

export CIVIL_SERVICE_DIR="$HOME/my-project/.civil-service"

Default location: ~/.local/share/civil-service/

Output

All command output goes to stdout. Redirect to a file if needed:

civil-service status > project-health.txt

History is automatically logged to $DATA_DIR/history.log with timestamps.

---

Powered by BytesAgain | bytesagain.com | [e-mail]